[MNG-1568] test-jar dependency clobbers transitive dependency

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0
• Component/s: Plugins and Lifecycle

Environment

Linux 2.6.10-gentoo-r4 #1 SMP Mon Jan 10 14:53:56 EST 2005 i686 AMD Athlon(tm) MP 2400+ AuthenticAMD GNU/Linux
java version "1.4.2_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05)
Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode)

• Assignee: Carlos Sanchez Gonzalez
• Reporter: Andrew Moore
• Created: 14/Nov/05 22:31
• Updated: 21/Nov/10 10:03
• Resolved: 28/May/06 13:23

Description

Specifying a test-jar dependency clobbers any transitive dependency on
that project.

eg

projectA publishes jar and test-jar
projectB depends on projectA.jar (scope compile)
projectC depends on projectB.jar (scope compile) and projectA.test-jar
(scope test)

In projectC, the test scoped projectA.test-jar dependency effectively
clobbers the compile scoped transitive dependency on projectA.jar. ie
projectA.jar is no longer in projectC's compile scope dependency list.

If I explicitly specify the projectA.jar compile dependency in the projectC POM it is resolved correctly.

There are currently other issues with test-jar dependency
resolution that may be related.

MNG-1378 <http://jira.codehaus.org/browse/MNG-1378>

According to Brett "It shouldn't be clobbered, as
the conflict ID for a dependency is group:artifact:type:classifier" but this isn't what I am seeing.

Issue Links

• duplicates: MNG-1895 Dependencies in two paths are not added to resolution when scope needs to be updated in the nearest due to any of nearest parents
• is duplicated by: MNG-1823 dependencies with classifier mask transitive dependencies of same dependency without classifier
• is related to: MNG-1571 Wrong calculation of transient dependecies if artifact is referenced from different scopes