[
http://jira.codehaus.org/browse/MPOM-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MNG-4880 to MPOM-2:
--------------------------------------
Complexity: (was: Intermediate)
Component/s: (was: Apache or Maven Parent poms)
Workflow: jira (was: Maven New)
Key: MPOM-2 (was: MNG-4880)
Project: Apache or Maven Parent POMs (was: Maven 2 & 3)
> apache-release does unwanted things in the prepare goal
> -------------------------------------------------------
>
> Key: MPOM-2
> URL: http://jira.codehaus.org/browse/MPOM-2
> Project: Apache or Maven Parent POMs
> Issue Type: Bug
> Reporter: Benson Margulies
>
> 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.
-
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
