svn commit: r1020711 - in /websites/staging/maven/trunk/content: ./ guides/development/guide-testing-releases.html maven-site-1.0-site.jar

[bu...@apache.org]

Author: buildbot
Date: Sat Nov 11 18:54:20 2017
New Revision: 1020711

Log:
Staging update by buildbot for maven

Modified:
    websites/staging/maven/trunk/content/   (props changed)
    websites/staging/maven/trunk/content/guides/development/guide-testing-releases.html
    websites/staging/maven/trunk/content/maven-site-1.0-site.jar

Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Nov 11 18:54:20 2017
@@ -1 +1 @@
-1814966
+1814967

Modified: websites/staging/maven/trunk/content/guides/development/guide-testing-releases.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/development/guide-testing-releases.html (original)
+++ websites/staging/maven/trunk/content/guides/development/guide-testing-releases.html Sat Nov 11 18:54:20 2017
@@ -196,7 +196,7 @@
   ...</pre></div>
 <p>With this in place, you can activate it by simply changing the plugin version to the one you are testing in the POM as above, then run the build with the following command:</p>
 <div>
-<pre>mvn clean install -Pstaged-releases</pre></div>
+<pre>mvn verify -Pstaged-releases</pre></div>
 <p>Note that the same conditions apply as above about cleaning out the local repository to prevent pollution of your local build environment.</p></div></div>
         </div>
       </div>

Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.