You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Rahul Akolkar (JIRA)" <ji...@apache.org> on 2008/03/21 00:01:25 UTC
[jira] Created: (COMMONSSITE-27) Change the
distributionManagement/repository contents in the release profile
Change the distributionManagement/repository contents in the release profile
----------------------------------------------------------------------------
Key: COMMONSSITE-27
URL: https://issues.apache.org/jira/browse/COMMONSSITE-27
Project: Commons All
Issue Type: Improvement
Components: Commons Parent Pom
Reporter: Rahul Akolkar
In order to facilitate staging releases. Patch coming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COMMONSSITE-27) Change the
distributionManagement/repository contents in the release profile
Posted by "Dennis Lundberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COMMONSSITE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581059#action_12581059 ]
Dennis Lundberg commented on COMMONSSITE-27:
--------------------------------------------
First we should establish a release process for releases with Maven 2 in commons. Then we can look at how to facilitate it in the parent pom.
> Change the distributionManagement/repository contents in the release profile
> ----------------------------------------------------------------------------
>
> Key: COMMONSSITE-27
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-27
> Project: Commons All
> Issue Type: Improvement
> Components: Commons Parent Pom
> Reporter: Rahul Akolkar
> Attachments: COMMONSSITE-27-01.patch
>
>
> In order to facilitate staging releases. Patch coming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COMMONSSITE-27) Change the
distributionManagement/repository contents in the release profile
Posted by "James Carman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COMMONSSITE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581061#action_12581061 ]
James Carman commented on COMMONSSITE-27:
-----------------------------------------
+1. There doesn't appear to be a consensus just yet. We started a Wiki page for figuring out the best practices for releasing using m2. Perhaps more work should be done on that?
> Change the distributionManagement/repository contents in the release profile
> ----------------------------------------------------------------------------
>
> Key: COMMONSSITE-27
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-27
> Project: Commons All
> Issue Type: Improvement
> Components: Commons Parent Pom
> Reporter: Rahul Akolkar
> Attachments: COMMONSSITE-27-01.patch
>
>
> In order to facilitate staging releases. Patch coming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COMMONSSITE-27) Change the
distributionManagement/repository contents in the release profile
Posted by "Rahul Akolkar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COMMONSSITE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580963#action_12580963 ]
Rahul Akolkar commented on COMMONSSITE-27:
------------------------------------------
I'd actually prefer if the repository ID was "apache.staging" (patch not updated).
> Change the distributionManagement/repository contents in the release profile
> ----------------------------------------------------------------------------
>
> Key: COMMONSSITE-27
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-27
> Project: Commons All
> Issue Type: Improvement
> Components: Commons Parent Pom
> Reporter: Rahul Akolkar
> Attachments: COMMONSSITE-27-01.patch
>
>
> In order to facilitate staging releases. Patch coming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COMMONSSITE-27) Change the
distributionManagement/repository contents in the release profile
Posted by "Rahul Akolkar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COMMONSSITE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rahul Akolkar updated COMMONSSITE-27:
-------------------------------------
Attachment: COMMONSSITE-27-01.patch
Suggested patch. Caveats:
(a) Will be a best practice to clean staging repo before every new RC
(b) Haven't verified that ${pom.version} gives us the correct version here (TODO)
> Change the distributionManagement/repository contents in the release profile
> ----------------------------------------------------------------------------
>
> Key: COMMONSSITE-27
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-27
> Project: Commons All
> Issue Type: Improvement
> Components: Commons Parent Pom
> Reporter: Rahul Akolkar
> Attachments: COMMONSSITE-27-01.patch
>
>
> In order to facilitate staging releases. Patch coming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (COMMONSSITE-27) Change the
distributionManagement/repository contents in the rc profile
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COMMONSSITE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebb resolved COMMONSSITE-27.
-----------------------------
Resolution: Won't Fix
Nexus renders this unnecessary
> Change the distributionManagement/repository contents in the rc profile
> -----------------------------------------------------------------------
>
> Key: COMMONSSITE-27
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-27
> Project: Commons All
> Issue Type: Improvement
> Components: Commons Parent Pom
> Reporter: Rahul Akolkar
> Attachments: COMMONSSITE-27-01.patch
>
>
> In order to facilitate staging releases. Patch coming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COMMONSSITE-27) Change the
distributionManagement/repository contents in the rc profile
Posted by "Rahul Akolkar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COMMONSSITE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rahul Akolkar updated COMMONSSITE-27:
-------------------------------------
Summary: Change the distributionManagement/repository contents in the rc profile (was: Change the distributionManagement/repository contents in the release profile)
Editing summary as change will be made to the rc profile as mentioned above.
> Change the distributionManagement/repository contents in the rc profile
> -----------------------------------------------------------------------
>
> Key: COMMONSSITE-27
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-27
> Project: Commons All
> Issue Type: Improvement
> Components: Commons Parent Pom
> Reporter: Rahul Akolkar
> Attachments: COMMONSSITE-27-01.patch
>
>
> In order to facilitate staging releases. Patch coming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COMMONSSITE-27) Change the
distributionManagement/repository contents in the release profile
Posted by "James Carman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COMMONSSITE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580965#action_12580965 ]
James Carman commented on COMMONSSITE-27:
-----------------------------------------
If this is in the "release" profile, why would the site be called "staging"? Shouldn't staging sites be for release candidates?
> Change the distributionManagement/repository contents in the release profile
> ----------------------------------------------------------------------------
>
> Key: COMMONSSITE-27
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-27
> Project: Commons All
> Issue Type: Improvement
> Components: Commons Parent Pom
> Reporter: Rahul Akolkar
> Attachments: COMMONSSITE-27-01.patch
>
>
> In order to facilitate staging releases. Patch coming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COMMONSSITE-27) Change the
distributionManagement/repository contents in the release profile
Posted by "Rahul Akolkar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COMMONSSITE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580966#action_12580966 ]
Rahul Akolkar commented on COMMONSSITE-27:
------------------------------------------
Thanks for bringing that up James, looking at ...
http://wiki.apache.org/commons/CreatingReleases
... I don't see the release profile being mentioned at all (other than the parent release), so I think you are right. I may have to go to the archives for the origin (and uses) of the "rc" and "release" profiles :-) (unless you know), but that will have to wait till after dinner.
> Change the distributionManagement/repository contents in the release profile
> ----------------------------------------------------------------------------
>
> Key: COMMONSSITE-27
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-27
> Project: Commons All
> Issue Type: Improvement
> Components: Commons Parent Pom
> Reporter: Rahul Akolkar
> Attachments: COMMONSSITE-27-01.patch
>
>
> In order to facilitate staging releases. Patch coming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COMMONSSITE-27) Change the
distributionManagement/repository contents in the release profile
Posted by "Rahul Akolkar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COMMONSSITE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581207#action_12581207 ]
Rahul Akolkar commented on COMMONSSITE-27:
------------------------------------------
OK then, detour:
http://markmail.org/message/3emjaadwpf7cr5q3
> Change the distributionManagement/repository contents in the release profile
> ----------------------------------------------------------------------------
>
> Key: COMMONSSITE-27
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-27
> Project: Commons All
> Issue Type: Improvement
> Components: Commons Parent Pom
> Reporter: Rahul Akolkar
> Attachments: COMMONSSITE-27-01.patch
>
>
> In order to facilitate staging releases. Patch coming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.