[ http://jira.codehaus.org/browse/MNG-1568?page=all ]
Carlos Sanchez closed MNG-1568:
-------------------------------
Assign To: Carlos Sanchez
Resolution: Duplicate
> test-jar dependency clobbers transitive dependency
> --------------------------------------------------
>
> Key: MNG-1568
> URL: http://jira.codehaus.org/browse/MNG-1568
> Project: Maven 2
> Type: Bug
> Components: Plugins and Lifecycle
> Versions: 2.0
> 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)
> Reporter: Andrew Moore
> Assignee: Carlos Sanchez
> Attachments: itMNG1568.tar.gz
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
