[MNG-4800] Conflict resolution does not pick sub tree of nearest dependency if farther conflicting dependency has wider scope

• 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
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 08/Sep/10 04:39
• Updated: 21/Nov/10 12:37
• Resolved: 13/Sep/10 04:34

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.

Issue Links

• is related to: MNG-4761 Plugin-level dependency scope causes some plugin classpaths to be incorrect
• is related to: MNG-4789 [regression] Difference in compile scope dependency resolution
• is related to: MNG-4790 Dependency resolution issue with provided scope
• relates to: MNG-3775 [regression] Problem in dependency resolution with exclusion, pom parent