[MNG-4134] Conflict resolution with scope widening can cause transitive dependencies to be omitted

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Affects Version/s: 2.1.0
• Component/s: Dependencies

Environment

Apache Maven 2.1.0 (r755702; 2009-03-18 19:10:27+0000)
Java version: 1.5.0_18
Java home: c:\Program Files (x86)\Java\jdk1.5.0_18\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows xp" version: "5.2" arch: "x86" Family: "windows"

• Assignee: Unassigned
• Reporter: Mark Hobson
• Created: 15/Apr/09 11:31
• Updated: 08/Feb/20 15:39
• Resolved: 22/Jan/14 20:31

Description

The attached zip contains the following project hierarchy:

p
+- a
|  \- b
|     \- x:2
|        \- y:1
+- c:runtime
|  \- d
|     \- y:2
+- e
   \- x:1

The expected resolved dependencies would be:

• test:a:jar:1:compile
• test:b:jar:1:compile
• test:c:jar:1:runtime
• test:d:jar:1:runtime
• test:e:jar:1:compile
• test:x:jar:1:compile
• test:y:jar:2:runtime

But running build.sh shows that test:y is omitted entirely. Note that changing the scope of c in p to compile shows the correct behaviour.

Issue Links

• relates to: MNG-4690 Transitive dependency lost when included another dependency
• relates to: MNG-4761 Plugin-level dependency scope causes some plugin classpaths to be incorrect