svn commit: r1561349 - /maven/plugins/trunk/maven-scm-publish-plugin/src/site/apt/usage.apt.vm

[hb...@apache.org]

Author: hboutemy
Date: Sat Jan 25 18:00:00 2014
New Revision: 1561349

URL: http://svn.apache.org/r1561349
Log:
fixed typos

Modified:
    maven/plugins/trunk/maven-scm-publish-plugin/src/site/apt/usage.apt.vm

Modified: maven/plugins/trunk/maven-scm-publish-plugin/src/site/apt/usage.apt.vm
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-scm-publish-plugin/src/site/apt/usage.apt.vm?rev=1561349&r1=1561348&r2=1561349&view=diff
==============================================================================
--- maven/plugins/trunk/maven-scm-publish-plugin/src/site/apt/usage.apt.vm (original)
+++ maven/plugins/trunk/maven-scm-publish-plugin/src/site/apt/usage.apt.vm Sat Jan 25 18:00:00 2014
@@ -30,26 +30,38 @@
 Usage
 
  The maven-scm-publish-plugin submits modified content to SCM, sites being the most classical case.
+
+ The standard use for sites is:
+
++-----------+
+mvn -Preporting site site:stage
+mvn scm-publish:publish-scm
++-----------+
+
+ which will work both for multi-and mono-modules sites.
+
+* Usage With Lifecycle (beta)
+
  There are two ways you can set this up for site in your POM.
 
-* Use the Custom Lifecycle
+  * Use the Custom Lifecycle
 
   Unfortunately, a Maven plugin can't define a top-level lifecycle
   like 'site'. However, it can come close. The plugin includes the 
   <scmpublish> goal. This goal does nothing except fork a custom
   <scmpublish> lifecycle, consisting of the following phases:
 
-  * <<<scmpublish-prepare>>>
+    ** <<<scmpublish-prepare>>>
 
-  * <<<scmpublish-pre-site>>>
+    ** <<<scmpublish-pre-site>>>
 
-  * <<<scmpublish-site>>>
+    ** <<<scmpublish-site>>>
 
-  * <<<scmpublish-post-site>>>
+    ** <<<scmpublish-post-site>>>
 
-  * <<<scmpublish-publish>>>
+    ** <<<scmpublish-publish>>>
 
-  []
+    []
 
   (Again unfortunately, Maven does not allow a custom lifecycle to share
   phases with some other lifecycle.)
@@ -83,7 +95,8 @@ Usage
 
   <Notice>: this is actually not working, the 003-lifecycle IT has been disabled.
 
-* Using the Site Lifecycle
+
+  * Using the Site Lifecycle
 
    The alternative is to attach the necessary activities to the site lifecycle and deactivate
    maven-site-plugin's site deploy goal. This requires more XML in the POM, but it may be easier