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

XML

Word

Printable

JSON

Type: Bug
Status: Closed
Priority: Major
Resolution: Incomplete
Affects Version/s: 2.1.0
Fix Version/s: None
Component/s: Dependencies
Labels:
None
Environment:

Hide
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"

Show
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"

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:

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.

relates to

MNG-4690 Transitive dependency lost when included another dependency

MNG-4761 Plugin-level dependency scope causes some plugin classpaths to be incorrect