[ http://jira.codehaus.org/browse/MRELEASE-129?page=comments#action_79529 ] Eric Bernstein commented on MRELEASE-129: -----------------------------------------
By default, the preparationGoals for a release:prepare are 'clean integration-test'. I believe your problem is that you really want them to be 'clean install'. You can configure this when configuring for the release plugin, but -D will probably work as well. Your problem might go away after configuring this. I do agree this is a bug, the prep goals 'clean integration-test' are really only appropriate for single module projects. I can't think of a way they would ever be desired for a multi-pom project. Changing the default would certainly affect backwards compatibility, but I cannot think of how it would actually hurt anyone. I'll upload a patch that changes the default just so my comment is complete... can anyone think of a reason not to change the default? > Release fails on EAR project with EJB module reference > ------------------------------------------------------ > > Key: MRELEASE-129 > URL: http://jira.codehaus.org/browse/MRELEASE-129 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Affects Versions: 2.0-beta-4 > Reporter: Mike Perham > Attachments: MRELEASE-129.patch > > > {code:xml} > <dependency> > <groupId>com.webify.fabric</groupId> > <artifactId>fabric-pm-mdb</artifactId> > <version>1.2.1</version> > <type>ejb</type> > </dependency> > {code} > During release:prepare, it transforms the POMs to the release version (as > above) and then runs the full build. The EAR build fails because the EJB > artifact is not installed to the local repo so it can't package that > dependent module by pulling it from the local repo. > [INFO] Failed to resolve artifact. > Missing: > ---------- > 1) com.webify.fabric:fabric-pm-mdb:ejb:1.2.1 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=com.webify.fabric > -DartifactId=fabric-pm-mdb \ > -Dversion=1.2.1 -Dpackaging=ejb -Dfile=/path/to/file > Path to dependency: > 1) com.webify.fabric:fabric-tools-ear:ear:4.1.1 > 2) com.webify.fabric:fabric-pm-mdb:ejb:1.2.1 > The workaround is to let it fail, run the build by hand to populate the local > repo and run the prepare goal again so it can find the binary. -- 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
