You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2015/03/29 18:02:18 UTC
[jira] (MRELEASE-874) Improve doc about specifying version of
plugin could sometimes be required on command-line
[ https://jira.codehaus.org/browse/MRELEASE-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-874.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.5.2
Assignee: Robert Scholte
Fixed in [r1669930|http://svn.apache.org/r1669930]
> Improve doc about specifying version of plugin could sometimes be required on command-line
> ------------------------------------------------------------------------------------------
>
> Key: MRELEASE-874
> URL: https://jira.codehaus.org/browse/MRELEASE-874
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 2.5
> Environment: online docs
> Reporter: Anders Hammar
> Assignee: Robert Scholte
> Fix For: 2.5.2
>
>
> On the page
> http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html
> it states the following command to execute when specifying a tag as well:
> {quote}
> mvn release:perform -DconnectionUrl=scm:svn:https://svn.apache.org/repos/asf/maven/plugins/tags/maven-release-plugin-2.0
> {quote}
> IMHO, in most scenarios when doing this one would do this outside of the project and Maven would then use the version om m-release-p specified in the super-POM of the executing Maven. Which could be an old version (Maven 3.0.4 specifies v2.0 of m-release-p for example).
> I suggest clearly explain this and also the command to use the latest version of the plugin, i.e.:
> {quote}
> mvn org.apache.maven.plugins:maven-release-plugin:<VERSION>:perform -DconnectionUrl=scm:svn:https://svn.apache.org/repos/asf/maven/plugins/tags/maven-release-plugin-2.0
> {quote}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)