[MNG-4854] [regression] ProjectSorter neglects conflicted versions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 3.0-alpha-6
• Component/s: Dependencies

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"

• Assignee: Benjamin Bentmann
• Reporter: Mark Hobson
• Created: 05/Oct/10 15:47
• Updated: 08/Feb/20 15:41
• Resolved: 05/Oct/10 16:06

Description

ProjectSorter 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.

Issue Links

• is related to: MNG-3814 Reactor builds fail due to erroneous cycle in project sorting which does not consider versions