You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/11/09 14:33:04 UTC

[jira] Updated: (MNG-4883) Maven 3.0 Breaks Version Range Support

     [ http://jira.codehaus.org/browse/MNG-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann updated MNG-4883:
-----------------------------------

    Component/s:     (was: Apache or Maven Parent poms)
                 Dependencies

> Maven 3.0 Breaks Version Range Support
> --------------------------------------
>
>                 Key: MNG-4883
>                 URL: http://jira.codehaus.org/browse/MNG-4883
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.0
>            Reporter: David Trott
>         Attachments: maven-samples.zip
>
>
> The sample project shows a usage of build ranges that should result in a build failure when you try to build project D.
> Because project D transitively depends on two different versions of project A 1.0 and 1.1.
> These versions are called out absolutely (using ranges) hence maven should not be able to build the project.
> This fails correctly in maven 2.2.1
> However the project builds successfully in maven 3.0
> Maven 3.0 should also fail to build.
> Note: I have included two copies of the pom file for project A so that you can build both of them without needing to edit the version.
> Build order is: A-1.0, A-1.1, B, C, D

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira