[
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
