maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1669930 - /maven/release/trunk/maven-release-plugin/src/site/apt/examples/perform-release.apt.vm
Date Sun, 29 Mar 2015 16:00:19 GMT
Author: rfscholte
Date: Sun Mar 29 16:00:19 2015
New Revision: 1669930

[MRELEASE-874] Improve doc about specifying version of plugin could sometimes be required
on command-line


Modified: maven/release/trunk/maven-release-plugin/src/site/apt/examples/perform-release.apt.vm
--- maven/release/trunk/maven-release-plugin/src/site/apt/examples/perform-release.apt.vm
+++ maven/release/trunk/maven-release-plugin/src/site/apt/examples/perform-release.apt.vm
Sun Mar 29 16:00:19 2015
@@ -45,11 +45,13 @@ mvn release:perform
   you need to give the goal the URL and an optional tag to perform the release from. For
-mvn release:perform -DconnectionUrl=scm:svn:
+mvn org.apache.maven.plugins:maven-release-plugin:${project.version}:perform -DconnectionUrl=scm:svn:
   <<<release:perform>>> will fork a new Maven instance to build the checked-out
project. This new Maven instance will use the
-  same system configuration and Maven profiles used by the one running the <<<release:perform>>>
+  same system configuration and Maven profiles used by the one running the <<<release:perform>>>
goal. Since there's no pom.xml, 
+  you should use the fully qualified name of the goal to ensure the right version of the
maven-release-plugin is used.
   It is possible to
   force some profiles to get enabled during release (for example to enable time-consuming
tasks that are only relevant
@@ -58,6 +60,7 @@ mvn release:perform -DconnectionUrl=scm:
+    <groupId>org.apache.maven.plugins</groupId>

View raw message