You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Tran (JIRA)" <ji...@codehaus.org> on 2008/11/18 12:14:41 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154565#action_154565 ] 

Dan Tran commented on MRELEASE-3:
---------------------------------

setting preparationGoals="clean install" will work, but for a large project with daily release, the build time is double.

> 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
>            Assignee: Emmanuel Venisse
>             Fix For: 2.0-beta-9
>
>
> 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