Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-4800

Conflict resolution does not pick sub tree of nearest dependency if farther conflicting dependency has wider scope

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.11, 2.2.1
    • Fix Version/s: 3.0
    • Component/s: Dependencies
    • Labels:
      None

      Description

      This is a follow-up for the observations made in MNG-4761 and MNG-4790 where scope widening during conflict resolution will cause inconsistent sub trees in the resolved dependency graph. For example the unresolved tree

      project
      +- a:runtime
      |  \- c:1:runtime
      |     \- x:runtime
      \- b:compile
         \- c:2:compile
            \- y:compile
      

      will be resolved to

      project
      +- a:runtime
      \- b:compile
         \- c:1:compile
            \- y:compile
      

      instead of

      project
      +- a:runtime
      |  \- c:1:compile
      |     \- x:compile
      \- b:compile
      

      Note the difference regarding inclusion of x/y. The latter tree structure is however successfully resolved when using compile scope for dependency a.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                bentmann Benjamin Bentmann
                Reporter:
                bentmann Benjamin Bentmann
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: