Maven 2 & 3

[regression] ProjectSorter neglects conflicted versions

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Not A Bug
  • Affects Version/s: 3.0-alpha-6
  • Fix Version/s: None
  • Component/s: Dependencies
  • Labels:
    None
  • Environment:
  • Complexity:
    Intermediate
  • Testcase included:
    yes
  • Number of attachments :
    1

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

Bug - A problem which impairs or prevents the functions of the product. MNG-3814 Reactor builds fail due to erroneous cycle in project sorting which does not consider versions

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Mark Hobson added a comment - - edited

Attached test method patch to demonstrate problem. This passes on the 2.2.x branch.

Show
Mark Hobson added a comment - - edited Attached test method patch to demonstrate problem. This passes on the 2.2.x branch.
Hide
Permalink
Benjamin Bentmann added a comment -

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.

Show
Benjamin Bentmann added a comment - 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.

People

  • Assignee:
    Benjamin Bentmann
    Reporter:
    Mark Hobson
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: