You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Olivier Lamy (JIRA)" <ji...@apache.org> on 2011/01/28 17:03:44 UTC
[jira] Created: (MPOM-1) apache-release does unwanted things in the
prepare goal
apache-release does unwanted things in the prepare goal
-------------------------------------------------------
Key: MPOM-1
URL: https://issues.apache.org/jira/browse/MPOM-1
Project: Maven POM
Issue Type: Bug
Reporter: Olivier Lamy
Release 7 of the org.apache:apache use -P to turn on an 'apache-release' profile in the release plugin. By using -P, this profile is turned on in prepare as well as perform.
This may turn into a contest of opinion, and you all may just tell me to jump in a lake, but I think this is a bad idea. At prepare time, we're just looking to get the versions setup and the tag made. Having to deal with gpg signing, and source archiving seems out of place.
At very least, I'd request that this the <arguments/> element be left out of the release plugin spec. If some project wants to use that particular collection of functions, fine. For the rest of us, who just want to get distribution management and other universals, you we wouldn't have to worry about it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (MPOM-1) apache-release does unwanted things in
the prepare goal
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox reopened MPOM-1:
--------------------------
This needs a different approach. If people don't want to use the profile by default, then lets put the profile argument into a property that can easily be overridden. It is very important though that we have proper release proceedures embodied by default in the ASF pom. People shouldn't have to customize sections of their poms to get proper releases. As it was done in the previous release, it "just works"
> apache-release does unwanted things in the prepare goal
> -------------------------------------------------------
>
> Key: MPOM-1
> URL: https://issues.apache.org/jira/browse/MPOM-1
> Project: Maven POM
> Issue Type: Bug
> Reporter: Olivier Lamy
> Assignee: Olivier Lamy
> Fix For: ASF-9
>
>
> Release 7 of the org.apache:apache use -P to turn on an 'apache-release' profile in the release plugin. By using -P, this profile is turned on in prepare as well as perform.
> This may turn into a contest of opinion, and you all may just tell me to jump in a lake, but I think this is a bad idea. At prepare time, we're just looking to get the versions setup and the tag made. Having to deal with gpg signing, and source archiving seems out of place.
> At very least, I'd request that this the <arguments/> element be left out of the release plugin spec. If some project wants to use that particular collection of functions, fine. For the rest of us, who just want to get distribution management and other universals, you we wouldn't have to worry about it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-1) apache-release does unwanted things in
the prepare goal
Posted by "Hervé Boutemy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hervé Boutemy updated MPOM-1:
-----------------------------
Fix Version/s: (was: ASF-10)
> apache-release does unwanted things in the prepare goal
> -------------------------------------------------------
>
> Key: MPOM-1
> URL: https://issues.apache.org/jira/browse/MPOM-1
> Project: Maven POMs
> Issue Type: Bug
> Components: asf
> Reporter: Olivier Lamy
> Assignee: Brian Fox
>
> Release 7 of the org.apache:apache use -P to turn on an 'apache-release' profile in the release plugin. By using -P, this profile is turned on in prepare as well as perform.
> This may turn into a contest of opinion, and you all may just tell me to jump in a lake, but I think this is a bad idea. At prepare time, we're just looking to get the versions setup and the tag made. Having to deal with gpg signing, and source archiving seems out of place.
> At very least, I'd request that this the <arguments/> element be left out of the release plugin spec. If some project wants to use that particular collection of functions, fine. For the rest of us, who just want to get distribution management and other universals, you we wouldn't have to worry about it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPOM-1) apache-release does unwanted things in the
prepare goal
Posted by "Olivier Lamy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed MPOM-1.
---------------------------
Resolution: Fixed
fixed rev 1065772
> apache-release does unwanted things in the prepare goal
> -------------------------------------------------------
>
> Key: MPOM-1
> URL: https://issues.apache.org/jira/browse/MPOM-1
> Project: Maven POM
> Issue Type: Bug
> Reporter: Olivier Lamy
> Assignee: Olivier Lamy
>
> Release 7 of the org.apache:apache use -P to turn on an 'apache-release' profile in the release plugin. By using -P, this profile is turned on in prepare as well as perform.
> This may turn into a contest of opinion, and you all may just tell me to jump in a lake, but I think this is a bad idea. At prepare time, we're just looking to get the versions setup and the tag made. Having to deal with gpg signing, and source archiving seems out of place.
> At very least, I'd request that this the <arguments/> element be left out of the release plugin spec. If some project wants to use that particular collection of functions, fine. For the rest of us, who just want to get distribution management and other universals, you we wouldn't have to worry about it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (MPOM-1) apache-release does unwanted things in
the prepare goal
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox reassigned MPOM-1:
----------------------------
Assignee: Brian Fox (was: Olivier Lamy)
> apache-release does unwanted things in the prepare goal
> -------------------------------------------------------
>
> Key: MPOM-1
> URL: https://issues.apache.org/jira/browse/MPOM-1
> Project: Maven POM
> Issue Type: Bug
> Reporter: Olivier Lamy
> Assignee: Brian Fox
> Fix For: ASF-9
>
>
> Release 7 of the org.apache:apache use -P to turn on an 'apache-release' profile in the release plugin. By using -P, this profile is turned on in prepare as well as perform.
> This may turn into a contest of opinion, and you all may just tell me to jump in a lake, but I think this is a bad idea. At prepare time, we're just looking to get the versions setup and the tag made. Having to deal with gpg signing, and source archiving seems out of place.
> At very least, I'd request that this the <arguments/> element be left out of the release plugin spec. If some project wants to use that particular collection of functions, fine. For the rest of us, who just want to get distribution management and other universals, you we wouldn't have to worry about it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-1) apache-release does unwanted things in
the prepare goal
Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benson Margulies updated MPOM-1:
--------------------------------
Fix Version/s: (was: ASF-9)
ASF-10
> apache-release does unwanted things in the prepare goal
> -------------------------------------------------------
>
> Key: MPOM-1
> URL: https://issues.apache.org/jira/browse/MPOM-1
> Project: Maven POM
> Issue Type: Bug
> Components: asf
> Reporter: Olivier Lamy
> Assignee: Brian Fox
> Fix For: ASF-10
>
>
> Release 7 of the org.apache:apache use -P to turn on an 'apache-release' profile in the release plugin. By using -P, this profile is turned on in prepare as well as perform.
> This may turn into a contest of opinion, and you all may just tell me to jump in a lake, but I think this is a bad idea. At prepare time, we're just looking to get the versions setup and the tag made. Having to deal with gpg signing, and source archiving seems out of place.
> At very least, I'd request that this the <arguments/> element be left out of the release plugin spec. If some project wants to use that particular collection of functions, fine. For the rest of us, who just want to get distribution management and other universals, you we wouldn't have to worry about it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPOM-1) apache-release does unwanted things in
the prepare goal
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993143#comment-12993143 ]
Brian Fox commented on MPOM-1:
------------------------------
A little history on this setup:
It was moved to the ASF pom from the Maven pom when we tried to provide correct defaults for all ASF projects built with Maven after a lengthy discussion on legal about minimal release requirements. The conclusion was to encapsulate best practices so projects that aren't maven experts can still get meet the release requirements.
This particular configuration of the release plugin dates back to the very first setup of the release profiles in the Maven pom, specifically added here: http://svn.apache.org/viewvc?view=revision&revision=502422 a little over 4 years ago.
> apache-release does unwanted things in the prepare goal
> -------------------------------------------------------
>
> Key: MPOM-1
> URL: https://issues.apache.org/jira/browse/MPOM-1
> Project: Maven POM
> Issue Type: Bug
> Reporter: Olivier Lamy
> Assignee: Brian Fox
> Fix For: ASF-9
>
>
> Release 7 of the org.apache:apache use -P to turn on an 'apache-release' profile in the release plugin. By using -P, this profile is turned on in prepare as well as perform.
> This may turn into a contest of opinion, and you all may just tell me to jump in a lake, but I think this is a bad idea. At prepare time, we're just looking to get the versions setup and the tag made. Having to deal with gpg signing, and source archiving seems out of place.
> At very least, I'd request that this the <arguments/> element be left out of the release plugin spec. If some project wants to use that particular collection of functions, fine. For the rest of us, who just want to get distribution management and other universals, you we wouldn't have to worry about it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPOM-1) apache-release does unwanted things in the
prepare goal
Posted by "Olivier Lamy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed MPOM-1.
---------------------------
Resolution: Fixed
Fix Version/s: ASF-9
> apache-release does unwanted things in the prepare goal
> -------------------------------------------------------
>
> Key: MPOM-1
> URL: https://issues.apache.org/jira/browse/MPOM-1
> Project: Maven POM
> Issue Type: Bug
> Reporter: Olivier Lamy
> Assignee: Olivier Lamy
> Fix For: ASF-9
>
>
> Release 7 of the org.apache:apache use -P to turn on an 'apache-release' profile in the release plugin. By using -P, this profile is turned on in prepare as well as perform.
> This may turn into a contest of opinion, and you all may just tell me to jump in a lake, but I think this is a bad idea. At prepare time, we're just looking to get the versions setup and the tag made. Having to deal with gpg signing, and source archiving seems out of place.
> At very least, I'd request that this the <arguments/> element be left out of the release plugin spec. If some project wants to use that particular collection of functions, fine. For the rest of us, who just want to get distribution management and other universals, you we wouldn't have to worry about it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPOM-1) apache-release does unwanted things in
the prepare goal
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993234#comment-12993234 ]
Hudson commented on MPOM-1:
---------------------------
Integrated in ASF Parent Pom #13 (See [https://hudson.apache.org/hudson/job/ASF%20Parent%20Pom/13/])
revert the site additions to the asf pom MPOM-1 MPOM-5 MPOM-7
> apache-release does unwanted things in the prepare goal
> -------------------------------------------------------
>
> Key: MPOM-1
> URL: https://issues.apache.org/jira/browse/MPOM-1
> Project: Maven POM
> Issue Type: Bug
> Reporter: Olivier Lamy
> Assignee: Brian Fox
> Fix For: ASF-9
>
>
> Release 7 of the org.apache:apache use -P to turn on an 'apache-release' profile in the release plugin. By using -P, this profile is turned on in prepare as well as perform.
> This may turn into a contest of opinion, and you all may just tell me to jump in a lake, but I think this is a bad idea. At prepare time, we're just looking to get the versions setup and the tag made. Having to deal with gpg signing, and source archiving seems out of place.
> At very least, I'd request that this the <arguments/> element be left out of the release plugin spec. If some project wants to use that particular collection of functions, fine. For the rest of us, who just want to get distribution management and other universals, you we wouldn't have to worry about it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (MPOM-1) apache-release does unwanted things in
the prepare goal
Posted by "Olivier Lamy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy reassigned MPOM-1:
-------------------------------
Assignee: Olivier Lamy
> apache-release does unwanted things in the prepare goal
> -------------------------------------------------------
>
> Key: MPOM-1
> URL: https://issues.apache.org/jira/browse/MPOM-1
> Project: Maven POM
> Issue Type: Bug
> Reporter: Olivier Lamy
> Assignee: Olivier Lamy
>
> Release 7 of the org.apache:apache use -P to turn on an 'apache-release' profile in the release plugin. By using -P, this profile is turned on in prepare as well as perform.
> This may turn into a contest of opinion, and you all may just tell me to jump in a lake, but I think this is a bad idea. At prepare time, we're just looking to get the versions setup and the tag made. Having to deal with gpg signing, and source archiving seems out of place.
> At very least, I'd request that this the <arguments/> element be left out of the release plugin spec. If some project wants to use that particular collection of functions, fine. For the rest of us, who just want to get distribution management and other universals, you we wouldn't have to worry about it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MPOM-1) apache-release does unwanted things in
the prepare goal
Posted by "Olivier Lamy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy reopened MPOM-1:
-----------------------------
> apache-release does unwanted things in the prepare goal
> -------------------------------------------------------
>
> Key: MPOM-1
> URL: https://issues.apache.org/jira/browse/MPOM-1
> Project: Maven POM
> Issue Type: Bug
> Reporter: Olivier Lamy
> Assignee: Olivier Lamy
> Fix For: ASF-9
>
>
> Release 7 of the org.apache:apache use -P to turn on an 'apache-release' profile in the release plugin. By using -P, this profile is turned on in prepare as well as perform.
> This may turn into a contest of opinion, and you all may just tell me to jump in a lake, but I think this is a bad idea. At prepare time, we're just looking to get the versions setup and the tag made. Having to deal with gpg signing, and source archiving seems out of place.
> At very least, I'd request that this the <arguments/> element be left out of the release plugin spec. If some project wants to use that particular collection of functions, fine. For the rest of us, who just want to get distribution management and other universals, you we wouldn't have to worry about it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPOM-1) apache-release does unwanted things in
the prepare goal
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993147#comment-12993147 ]
Hudson commented on MPOM-1:
---------------------------
Integrated in ASF Parent Pom #12 (See [https://hudson.apache.org/hudson/job/ASF%20Parent%20Pom/12/])
revert r1065772 see MPOM-1 for updated information
> apache-release does unwanted things in the prepare goal
> -------------------------------------------------------
>
> Key: MPOM-1
> URL: https://issues.apache.org/jira/browse/MPOM-1
> Project: Maven POM
> Issue Type: Bug
> Reporter: Olivier Lamy
> Assignee: Brian Fox
> Fix For: ASF-9
>
>
> Release 7 of the org.apache:apache use -P to turn on an 'apache-release' profile in the release plugin. By using -P, this profile is turned on in prepare as well as perform.
> This may turn into a contest of opinion, and you all may just tell me to jump in a lake, but I think this is a bad idea. At prepare time, we're just looking to get the versions setup and the tag made. Having to deal with gpg signing, and source archiving seems out of place.
> At very least, I'd request that this the <arguments/> element be left out of the release plugin spec. If some project wants to use that particular collection of functions, fine. For the rest of us, who just want to get distribution management and other universals, you we wouldn't have to worry about it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPOM-1) apache-release does unwanted things in
the prepare goal
Posted by "Olivier Lamy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993145#comment-12993145 ]
Olivier Lamy commented on MPOM-1:
---------------------------------
Brian : I agree on your revert np
> apache-release does unwanted things in the prepare goal
> -------------------------------------------------------
>
> Key: MPOM-1
> URL: https://issues.apache.org/jira/browse/MPOM-1
> Project: Maven POM
> Issue Type: Bug
> Reporter: Olivier Lamy
> Assignee: Brian Fox
> Fix For: ASF-9
>
>
> Release 7 of the org.apache:apache use -P to turn on an 'apache-release' profile in the release plugin. By using -P, this profile is turned on in prepare as well as perform.
> This may turn into a contest of opinion, and you all may just tell me to jump in a lake, but I think this is a bad idea. At prepare time, we're just looking to get the versions setup and the tag made. Having to deal with gpg signing, and source archiving seems out of place.
> At very least, I'd request that this the <arguments/> element be left out of the release plugin spec. If some project wants to use that particular collection of functions, fine. For the rest of us, who just want to get distribution management and other universals, you we wouldn't have to worry about it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MPOM-1) apache-release does unwanted things in
the prepare goal
Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MPOM-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benson Margulies updated MPOM-1:
--------------------------------
Component/s: asf
> apache-release does unwanted things in the prepare goal
> -------------------------------------------------------
>
> Key: MPOM-1
> URL: https://issues.apache.org/jira/browse/MPOM-1
> Project: Maven POM
> Issue Type: Bug
> Components: asf
> Reporter: Olivier Lamy
> Assignee: Brian Fox
> Fix For: ASF-9
>
>
> Release 7 of the org.apache:apache use -P to turn on an 'apache-release' profile in the release plugin. By using -P, this profile is turned on in prepare as well as perform.
> This may turn into a contest of opinion, and you all may just tell me to jump in a lake, but I think this is a bad idea. At prepare time, we're just looking to get the versions setup and the tag made. Having to deal with gpg signing, and source archiving seems out of place.
> At very least, I'd request that this the <arguments/> element be left out of the release plugin spec. If some project wants to use that particular collection of functions, fine. For the rest of us, who just want to get distribution management and other universals, you we wouldn't have to worry about it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira