[jira] Reopened: (MNG-4899) strange behavior during the dependency resolution

[ http://jira.codehaus.org/browse/MNG-4899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raffaele Verre reopened MNG-4899: - Sorry David Julian says: " Maven recognizes versions that match the following pattern:

[jira] Created: (MNG-4899) strange behavior during the dependency resolution

strange behavior during the dependency resolution - Key: MNG-4899 URL: http://jira.codehaus.org/browse/MNG-4899 Project: Maven 2 & 3 Issue Type: Bug Components: Dependencies

[jira] Commented: (MNG-4881) Problem resolving dependency range with SNAPSHOT

[ http://jira.codehaus.org/browse/MNG-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241444#action_241444 ] Raffaele Verre commented on MNG-4881: - sorry but it means that the method of resolution has changed

[jira] Reopened: (MNG-4881) Problem resolving dependency range with SNAPSHOT

[ http://jira.codehaus.org/browse/MNG-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raffaele Verre reopened MNG-4881: - maven2 works differently than maven3? Maven2 resolve the dipendency without problems with the last alpha >

[jira] Created: (MNG-4881) Problem resolving dependency range with SNAPSHOT

Problem resolving dependency range with SNAPSHOT Key: MNG-4881 URL: http://jira.codehaus.org/browse/MNG-4881 Project: Maven 2 & 3 Issue Type: Bug Components: Dependencies Affects

[jira] Created: (MNG-4681) Version range resolution problem

Version range resolution problem Key: MNG-4681 URL: http://jira.codehaus.org/browse/MNG-4681 Project: Maven 2 & 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.0-bet

[jira] Created: (SCM-506) Read scmVersion directly from pom

Read scmVersion directly from pom - Key: SCM-506 URL: http://jira.codehaus.org/browse/SCM-506 Project: Maven SCM Issue Type: Improvement Components: maven-plugin Affects Versions: 1.2, 1.1, 1.0