[ http://jira.codehaus.org/browse/MRELEASE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158512#action_158512 ]
David J. M. Karlsen commented on MRELEASE-264: ---------------------------------------------- Here is a thread which show's how this is a problem when using the dependency plugin w/ a dependency from the reactor build: http://www.nabble.com/release%3Aprepare-amusement-with-the-dependency-plugin-td21063104.html > "prepare" mojo calls "package", not "install" > --------------------------------------------- > > Key: MRELEASE-264 > URL: http://jira.codehaus.org/browse/MRELEASE-264 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Affects Versions: 2.0-beta-4 > Reporter: Stefan Behnel > > The "prepare" mojo calls "mvn package" for the build after adapting the POM > versions. This results in build failures if the project has interdependencies > between modules (a rather common case). The problem is that the new version > has not been deployed so far, so the required module artifacts are not yet > available from the repository. > The mojo should call "mvn install" to make artifacts available to the running > build process. -- 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