[
http://jira.codehaus.org/browse/MRELEASE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221171#action_221171
]
Wendy Smoak commented on MRELEASE-558:
--------------------------------------
I'm not sure you'll know the final release repository when the release is
staged.
And that repo could change in the meantime, if someone else deploys a release.
(Say you are working on 2.1 and they release 3.0 after you stage and before you
promote.)
I think the metadata should be done when the release is promoted.
> release:stage should merge metadata from repository.
> ----------------------------------------------------
>
> Key: MRELEASE-558
> URL: http://jira.codehaus.org/browse/MRELEASE-558
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: stage
> Affects Versions: 2.0
> Reporter: Antonio Petrelli
>
> Currently the release:stage goal does its job well, except when creating
> metadata.
> The metadata contains only the version of the released artifacts. I think
> that it should:
> * download the original metadata;
> * merge the metadata with the new one;
> * upload it in the staging repository.
> This way, moving from stage repository to the release repository is a matter
> of a simple copy. This is true especially at Apache.
--
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
