[
http://jira.codehaus.org/browse/MRELEASE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162808#action_162808
]
Thiago Leão Moreira commented on MRELEASE-264:
----------------------------------------------
The workaround proposed by Olivier is no working at least for 2.0-beta7 and
2.0-beta8 versions. The method mergeCommandLineConfig of the PrepareReleaseMojo
class only merge the releaseVersions and developmentVersions properties
obtained from the command line.
Why the other properties aren't been overwrite with the values obtained from
the command line??
> "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
> 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.
-
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
