You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Antonio Petrelli (JIRA)" <ji...@codehaus.org> on 2010/05/13 21:27:12 UTC
[jira] Created: (MRELEASE-558) release:stage should merge metadata
from repository.
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
[jira] Commented: (MRELEASE-558) release:stage should merge
metadata from repository.
Posted by "Joerg Schaible (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221215#action_221215 ]
Joerg Schaible commented on MRELEASE-558:
-----------------------------------------
bq. The only case it could happen is when someone releases from a branch and from the trunk.
Which happpens e.g. for the time being always with Apache commons dbcp: 1.4.x is Java 6 compatible, 1.3.x is for Java 5/1.4.
> 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
[jira] Closed: (MRELEASE-558) release:stage should merge metadata
from repository.
Posted by "Antonio Petrelli (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli closed MRELEASE-558.
-------------------------------------
Resolution: Won't Fix
The proposed solution gives more problems than the ones it wants to resolve. Closed as won't fix.
> 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
[jira] Commented: (MRELEASE-558) release:stage should merge
metadata from repository.
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRELEASE-558) release:stage should merge
metadata from repository.
Posted by "Antonio Petrelli (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221218#action_221218 ]
Antonio Petrelli commented on MRELEASE-558:
-------------------------------------------
Got the point Joerg :-D I close this issue since it has no meaning them. I'll open a thread at the Maven Developers ML about how to address the most annoying thing: the need of downloading and re-uploading the artifacts I already uploaded in the server when using the stage plugin.
> 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
[jira] Commented: (MRELEASE-558) release:stage should merge
metadata from repository.
Posted by "Antonio Petrelli (JIRA)" <ji...@codehaus.org>.
[ 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