[MNG-820] Over-zealous transitive dependencies during mediation

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.0-beta-1
• Fix Version/s: 2.0-beta-2
• Component/s: Artifacts and Repositories
• Environment: Windows XP, Cygwin
• Assignee: Brett Porter
• Reporter: Mark Hobson
• Created: 01/Sep/05 07:49
• Updated: 08/Feb/20 15:39
• Resolved: 26/Sep/05 00:52

Description

The attached zip sets up the following project hierarchy:

main.war
   projecta
      shared:1.0
         librarya
   projectb
      projectc
         shared:2.0
            libraryb

From what I understand of dependency mediation shared:2.0 should be chosen in preference to shared:1.0, and hence libraryb should be included instead of librarya. Using the latest m2 the main.war WEB-INF/lib contains:

projecta
projectb
projectc
shared:2.0
librarya
libraryb

Thus librarya is included when it shouldn't be.

Issue Links

• relates to: MNG-4768 Depending on declaration order, nearest matching version does not win when version range is involved in conflict
• relates to: MNG-4790 Dependency resolution issue with provided scope