[
https://jira.codehaus.org/browse/MRELEASE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281049#comment-281049
]
Robert Klaus commented on MRELEASE-264:
---------------------------------------
Well I think I stumpled upon this as well. For all users of the dependency
plugin you might want to use the 2.3 version where the goals {{copy}} and
{{unpack}} can resolve in the reactor. See MDEP-316
> "prepare" mojo calls "package", not "install"
> ---------------------------------------------
>
> Key: MRELEASE-264
> URL: https://jira.codehaus.org/browse/MRELEASE-264
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: stage
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
