You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stefan Behnel (JIRA)" <ji...@codehaus.org> on 2007/07/10 17:33:13 UTC
[jira] Commented: (MRELEASE-264) "prepare" mojo calls "package",
not "install"
[ http://jira.codehaus.org/browse/MRELEASE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101817 ]
Stefan Behnel commented on MRELEASE-264:
----------------------------------------
This actually affects 2.0.4.
> "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