[ http://jira.codehaus.org/browse/MNG-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4854. ---------------------------------- Resolution: Not A Bug Assignee: Benjamin Bentmann If {{project:1.0}} depends on {{dependency:2.0}} then it doesn't depend on {{dependency:1.0}}. See MNG-3814 for more details why versions matter. > [regression] ProjectSorter neglects conflicted versions > ------------------------------------------------------- > > Key: MNG-4854 > URL: http://jira.codehaus.org/browse/MNG-4854 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies > Affects Versions: 3.0-alpha-6 > Environment: Apache Maven 3.0 (r1004208; 2010-10-04 12:50:56+0100) > Java version: 1.5.0_22 > Java home: C:\Program Files (x86)\Java\jdk1.5.0_22\jre > Default locale: en_GB, platform encoding: Cp1252 > OS name: "windows xp" version: "5.2" arch: "x86" Family: "windows" > Reporter: Mark Hobson > Assignee: Benjamin Bentmann > Attachments: MNG-4854-test.patch > > > [ProjectSorter|http://svn.apache.org/repos/asf/maven/maven-3/trunk/maven-core/src/main/java/org/apache/maven/project/ProjectSorter.java] > skips vertexes where versions don't match and thus produces incorrect > results. > For example, if A depends on B:1.0 but B is resolved to 1.1 (via conflict > resolution or dependency management) then A->B:1.0 is lost. One suspect > could be {{isSpecificVersion}} which returns true for 1.0, which isn't a > specific version like [1.0], so this vertex gets lost as B:1.0 doesn't exist. -- 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