You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Baerrach bonDierne (JIRA)" <ji...@codehaus.org> on 2007/01/02 06:11:10 UTC
[jira] Commented: (MRELEASE-3) release:prepare should not require
multimodule artifacts to be in the local repository
[ http://jira.codehaus.org/browse/MRELEASE-3?page=comments#action_83778 ]
Baerrach bonDierne commented on MRELEASE-3:
-------------------------------------------
MRELEASE-182 (release:prepare preparationGoals should be "clean verify") may be related to this issue.
I disagree with the recommendation in MRELEASE-182 as I believe that "install" needs to happen as part of release:prepare.
The scenario is this:
* module projects are executed with existing default goals (clean integration-test)
* deployment module gets executed which has an assembly which attempts to collect all the previous module artifact's and place them into a distributable archive.
The deployment module will fail since none of the artifacts are available in the local repository.
According to http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html:
"package" < "integration-test" < "install" and hence the deployment module will cause failures in the release process.
My workaround is to manually run mvn install when the release process fails and then to restart the release.
> release:prepare should not require multimodule artifacts to be in the local repository
> --------------------------------------------------------------------------------------
>
> Key: MRELEASE-3
> URL: http://jira.codehaus.org/browse/MRELEASE-3
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Reporter: John Casey
>
> Currently, if you try to run release:prepare on a multimodule project after removing any of that build's artifacts from the local repository, it will fail. Investigate why release:prepare needs the multimodule artifacts installed in the local repository before it can succeed.
> To reproduce, comment the following line in it2002/test.sh:
> mvn clean install
> NOTE: This may have to do with the version resolution code, which is used to resolve SNAPSHOT versions.
--
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