maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Petrelli (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRELEASE-558) release:stage should merge metadata from repository.
Date Fri, 14 May 2010 08:07:12 GMT

    [ http://jira.codehaus.org/browse/MRELEASE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221208#action_221208
] 

Antonio Petrelli commented on MRELEASE-558:
-------------------------------------------

About the finaly release repository, it *is* known. Probably not the HTTP repository, but
the repository where it is should be deployed is known by reading the "developerConnection"
value. Probably it can be downloaded from there.
About the double release, I think it is unlikely to happen. The only case it could happen
is when someone releases from a branch and from the trunk.

> 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

        

Mime
View raw message