You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/03/26 17:56:23 UTC
[jira] Closed: (MNG-4610) Bump maven-release-plugin to v2.0 in
super POM
[ http://jira.codehaus.org/browse/MNG-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4610.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0-alpha-8
Assignee: Benjamin Bentmann
Done in [r927965|http://svn.apache.org/viewvc?view=revision&revision=927965]. Still, given that most of the Release Plugin goals require a POM, you're in rather good position to just control the plugin version yourself.
> Bump maven-release-plugin to v2.0 in super POM
> ----------------------------------------------
>
> Key: MNG-4610
> URL: http://jira.codehaus.org/browse/MNG-4610
> Project: Maven 2 & 3
> Issue Type: Improvement
> Affects Versions: 3.0-alpha-7
> Environment: n/a
> Reporter: Anders Hammar
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-8
>
>
> Change the default version of maven-release-plugin to 2.0 in the super POM.
> The background for this request is that v2.0-beta-9 doesn't have signatures and I have some customers requiring signature verification for Apache artifacts. As some Maven commands are run outside of a POM, the default version would be used. Which doesn't work in this case.
--
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