[jira] (MNG-3092) resolution of version ranges with non-snapshot bounds can resolve to a snapshot version

[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350960#comment-350960 ] Richard Vowles commented on MNG-3092: - Yes @Sergei, however you are releasing that snapshot are y

[jira] (MNG-3092) resolution of version ranges with non-snapshot bounds can resolve to a snapshot version

[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350957#comment-350957 ] Richard Vowles commented on MNG-3092: - @Sergei - disk space is cheap - and its a build server, so

[jira] (MNG-3092) resolution of version ranges with non-snapshot bounds can resolve to a snapshot version

[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350950#comment-350950 ] Richard Vowles commented on MNG-3092: - We use, and many others use Maven version ranges with plea

[jira] (MNG-3092) resolution of version ranges with non-snapshot bounds can resolve to a snapshot version

[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350883#comment-350883 ] Richard Vowles commented on MNG-3092: - Excuse me if I am not understand you here Sergei. Are you

[jira] (MNG-3092) resolution of version ranges with non-snapshot bounds can resolve to a snapshot version

[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350880#comment-350880 ] Richard Vowles commented on MNG-3092: - Its not an easy fix when so many people work perfectly wel

[jira] (MNG-3092) resolution of version ranges with non-snapshot bounds can resolve to a snapshot version

[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350874#comment-350874 ] Richard Vowles commented on MNG-3092: - No, of course I am not being sarcastic. We use version ran

[jira] (MNG-3092) resolution of version ranges with non-snapshot bounds can resolve to a snapshot version

[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350852#comment-350852 ] Richard Vowles commented on MNG-3092: - The current functionality works fine, change the spec, tha

[jira] (MDEP-398) Dependency resolution error with Maven 3

[ https://jira.codehaus.org/browse/MDEP-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349471#comment-349471 ] Richard Vowles commented on MDEP-398: - it seems to have resolved itself in later versions of Mave

[jira] (MDEP-398) Dependency resolution error with Maven 3

[ https://jira.codehaus.org/browse/MDEP-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349406#comment-349406 ] Richard Vowles commented on MDEP-398: - this issue can close. > Dependency resolution error with

[jira] (MNG-5433) Maven 3

[ https://jira.codehaus.org/browse/MNG-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Vowles updated MNG-5433: Attachment: m3-dep2.1-tree-success.txt m3-dep2.1-tree-success.pom missed these two first t

[jira] (MNG-5433) Maven 3

Richard Vowles created MNG-5433: --- Summary: Maven 3 Key: MNG-5433 URL: https://jira.codehaus.org/browse/MNG-5433 Project: Maven 2 & 3 Issue Type: Bug Components: Dependencies Affe

[jira] Updated: (MNG-5084) Resolver for plugins failing

[ http://jira.codehaus.org/browse/MNG-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Vowles updated MNG-5084: Attachment: Screen shot 2011-05-12 at 10.43.05 PM.png demonstrating debug information showing unresolved ar

[jira] Commented: (MNG-5084) Resolver for plugins failing

[ http://jira.codehaus.org/browse/MNG-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266470#action_266470 ] Richard Vowles commented on MNG-5084: - What is strange about the groovy artefact is this appears to

[jira] Commented: (MNG-5084) Resolver for plugins failing

[ http://jira.codehaus.org/browse/MNG-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266465#action_266465 ] Richard Vowles commented on MNG-5084: - I have now spent some hours debugging through aether-1.11 (w

[jira] Commented: (MNG-5084) Resolver for plugins failing

[ http://jira.codehaus.org/browse/MNG-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265326#action_265326 ] Richard Vowles commented on MNG-5084: - It also appears that the behavior is such, that when you do

[jira] Created: (MNG-5084) Resolver for plugins failing

Resolver for plugins failing Key: MNG-5084 URL: http://jira.codehaus.org/browse/MNG-5084 Project: Maven 2 & 3 Issue Type: Bug Components: Dependencies Affects Versions: 3.0.3 Environment: J

[jira] Commented: (MNG-2742) Using a version range in a plugin dependency causes "failure to resolve artifact" error

[ http://jira.codehaus.org/browse/MNG-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262296#action_262296 ] Richard Vowles commented on MNG-2742: - This has been true since 2.0.4? You *have* to be kidding! I