You can add it to that, or better create a new issue and link to the original/mention it in the description. It shouldn't be clobbered, as the conflict ID for a dependency is group:artifact:type:classifier.
- Brett On 11/15/05, andrew <[EMAIL PROTECTED]> wrote: > Maven version: 2.0 > > Hi, > > 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. > > I see that there are currently other issues with test-jar dependency > resolution (MNG-1378 <http://jira.codehaus.org/browse/MNG-1378>). > > Should I add the above to the current issue, create a new one OR should > I really be doing this some other way? > > Thanks, > ...andrew > -- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
