[ http://jira.codehaus.org/browse/MJAR-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120463 ]
Chad Lyon commented on MJAR-68: ------------------------------- The problem is actually in the resolution of dependencies. I have a multi-module project. The project packages up a test JAR in the first module in the reactor order. This JAR is needed by the tests of the other modules. If my local repository is clean and I try to build while specifying -Dmaven.test.skip=true then two things happen that cause the build to fail: -The building of the test JAR is skipped because tests are skipped. -Skipping of tests does not instruct the dependency resolver for the other modules to NOT download the test JAR of the first module. Thus, I must first get the test-jar packaged up and in my local repo before my build can succeed. I can either run with tests or specify -Dmaven.test.execute=false I think the proper fix for this would be to fix the resolution of dependencies. Basically, if tests are skipped then don't check for deps that are scope=test. This problem seems to be related to MJAR-90. I bet before this fix went in this issue didn't exist. > multi module release fails because of test-jar > ---------------------------------------------- > > Key: MJAR-68 > URL: http://jira.codehaus.org/browse/MJAR-68 > Project: Maven 2.x Jar Plugin > Issue Type: Bug > Affects Versions: 2.1 > Environment: maven 2.0.5 > Reporter: Yuri Schimke > > The release plugin is failing in the prepare task > mvn release:prepare > seemingly because it can't find the test-jar that has just been built by the > previous module i.e. built within. > Are there some examples in the wild of using the test-jar on a multi module > project that does releases? > The (nasty) workaround I have for now, is to wait for the build to fail and > then > mvn install > So the test-jar (and other artifacts) are in my local repository and then > continue > mvn release:prepare -- 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