[jira] Commented: (MNG-3043) Allow 'mvn test' to work with test-jar dependencies in a reactor
[ http://jira.codehaus.org/browse/MNG-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168369#action_168369 ] Benjamin Bentmann commented on MNG-3043: Feature branch has been created for [discussion on dev@|http://www.nabble.com/MNG-3043%2C-please-comment-to22388639.html]. > Allow 'mvn test' to work with test-jar dependencies in a reactor > > > Key: MNG-3043 > URL: http://jira.codehaus.org/browse/MNG-3043 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies, Reactor and workspace >Affects Versions: 2.0.6, 2.0.7 >Reporter: Kenney Westerhof > Fix For: 2.0.x > > Attachments: mng-3043.zip > > > Basically the issue is demonstrated by MNG-2045, but instead of running 'mvn > install', you run 'mvn test'. > Test classes of dependencies should be resolved from the reactor, just as > main classes, if there's no archive available. > I'm not sure how to go about this. Specifying a dependency on something with > test-jar, > and having that dependency declare the maven-jar-plugin with the 'test-jar' > goal is insufficient. > Perhaps we can just add a standard classifier that maven is aware of, in this > case 'tests'. The jar packaging > would export this as a known classifier, and tells maven how it contributes > to what classpath. > Since test sources are a first class citizen, just as main sources are (they > have the same phases, same > elements in the pom (but differently named)). > It seems logical to me that somehow the test classes should be made available > to dependencies, > if they declare a dependency with classifier 'tests'. -- 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
[jira] Commented: (MNG-3043) Allow 'mvn test' to work with test-jar dependencies in a reactor
[ http://jira.codehaus.org/browse/MNG-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104926 ] Piotr Tabor commented on MNG-3043: -- Kenney, could you check if your problem is resolved with current (SVN/SNAPSHOT) version of maven-jar-plugin. I hope MJAR-75 that was fixed, resolved this issue too. Thank you > Allow 'mvn test' to work with test-jar dependencies in a reactor > > > Key: MNG-3043 > URL: http://jira.codehaus.org/browse/MNG-3043 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies, Reactor and workspace >Affects Versions: 2.0.6, 2.0.7, 2.1 >Reporter: Kenney Westerhof > Fix For: Reviewed Pending Version Assignment > > > Basically the issue is demonstrated by MNG-2045, but instead of running 'mvn > install', you run 'mvn test'. > Test classes of dependencies should be resolved from the reactor, just as > main classes, if there's no archive available. > I'm not sure how to go about this. Specifying a dependency on something with > test-jar, > and having that dependency declare the maven-jar-plugin with the 'test-jar' > goal is insufficient. > Perhaps we can just add a standard classifier that maven is aware of, in this > case 'tests'. The jar packaging > would export this as a known classifier, and tells maven how it contributes > to what classpath. > Since test sources are a first class citizen, just as main sources are (they > have the same phases, same > elements in the pom (but differently named)). > It seems logical to me that somehow the test classes should be made available > to dependencies, > if they declare a dependency with classifier 'tests'. -- 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
[jira] Commented: (MNG-3043) Allow 'mvn test' to work with test-jar dependencies in a reactor
[ http://jira.codehaus.org/browse/MNG-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103791 ] Basil James Whitehouse III commented on MNG-3043: - This also seems to affect the Release plugin when performing a release:prepare. > Allow 'mvn test' to work with test-jar dependencies in a reactor > > > Key: MNG-3043 > URL: http://jira.codehaus.org/browse/MNG-3043 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies, Reactor and workspace >Affects Versions: 2.0.6, 2.0.7, 2.1 >Reporter: Kenney Westerhof > Fix For: Reviewed Pending Version Assignment > > > Basically the issue is demonstrated by MNG-2045, but instead of running 'mvn > install', you run 'mvn test'. > Test classes of dependencies should be resolved from the reactor, just as > main classes, if there's no archive available. > I'm not sure how to go about this. Specifying a dependency on something with > test-jar, > and having that dependency declare the maven-jar-plugin with the 'test-jar' > goal is insufficient. > Perhaps we can just add a standard classifier that maven is aware of, in this > case 'tests'. The jar packaging > would export this as a known classifier, and tells maven how it contributes > to what classpath. > Since test sources are a first class citizen, just as main sources are (they > have the same phases, same > elements in the pom (but differently named)). > It seems logical to me that somehow the test classes should be made available > to dependencies, > if they declare a dependency with classifier 'tests'. -- 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
