You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2011/08/06 18:32:27 UTC

[jira] [Updated] (MPOM-1) apache-release does unwanted things in the prepare goal

     [ 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