Author: rfscholte
Date: Tue Apr 24 20:06:22 2012
New Revision: 1329985
URL: http://svn.apache.org/viewvc?rev=1329985&view=rev
Log:
Fix MRELEASE-698: Inconsistent documentation for 'generate release pom'
Modified:
maven/release/trunk/maven-release-plugin/src/site/apt/examples/generate-release-poms.apt
Modified:
maven/release/trunk/maven-release-plugin/src/site/apt/examples/generate-release-poms.apt
URL:
http://svn.apache.org/viewvc/maven/release/trunk/maven-release-plugin/src/site/apt/examples/generate-release-poms.apt?rev=1329985&r1=1329984&r2=1329985&view=diff
==============================================================================
---
maven/release/trunk/maven-release-plugin/src/site/apt/examples/generate-release-poms.apt
(original)
+++
maven/release/trunk/maven-release-plugin/src/site/apt/examples/generate-release-poms.apt
Tue Apr 24 20:06:22 2012
@@ -28,18 +28,18 @@
Generate Release POMs
To generate POMs with resolved information (e.g. version numbers) to check
the values that the Release Plugin will use,
- set the property <<<generateReleasePoms>>> to <<<true>>>. Resolved values
will be saved in <<<release-pom.xml>>>.
+ execute the <<<prepare-with-pom>>> goal. Resolved values will be saved in
<<<release-pom.xml>>>.
--------
-mvn release:prepare -DgenerateReleasePoms=true
--------
++-------
+mvn release:prepare-with-pom
++-------
This relies on <<<release.properties>>> being present from a previous
release preparation. If this is not the case,
you need to give the goal the name of the URL and optional tag to perform
the release from. For example:
--------
-mvn release:prepare -DgenerateReleasePoms=true
++-------
+mvn release:prepare-with-pom
-DconnectionUrl=scm:svn:https://svn.apache.org/repos/asf/maven/plugins/tags/maven-release-plugin-2.0
--------
++-------
After the release is complete, the <<<release.properties>>> and other
release files will be removed from the checkout.
