svn commit: r1359925 - /maven/sandbox/trunk/plugins/maven-scm-publish-plugin/src/site/apt/index.apt

[hb...@apache.org]

Author: hboutemy
Date: Tue Jul 10 21:59:39 2012
New Revision: 1359925

URL: http://svn.apache.org/viewvc?rev=1359925&view=rev
Log:
added info on empty directory creation in svn case

Modified:
    maven/sandbox/trunk/plugins/maven-scm-publish-plugin/src/site/apt/index.apt

Modified: maven/sandbox/trunk/plugins/maven-scm-publish-plugin/src/site/apt/index.apt
URL: http://svn.apache.org/viewvc/maven/sandbox/trunk/plugins/maven-scm-publish-plugin/src/site/apt/index.apt?rev=1359925&r1=1359924&r2=1359925&view=diff
==============================================================================
--- maven/sandbox/trunk/plugins/maven-scm-publish-plugin/src/site/apt/index.apt (original)
+++ maven/sandbox/trunk/plugins/maven-scm-publish-plugin/src/site/apt/index.apt Tue Jul 10 21:59:39 2012
@@ -76,12 +76,13 @@ Known Limitations
 
     There are 2 known limitations:
     
-    * <<the plugin doesn't create the initial SCM directory>>, it just import content into an
-    existing SCM directory,
+    * <<the plugin doesn't create the initial SCM directory>>, it just updates content from an
+    existing SCM directory. Then you need to manually create the empty directory first
+    (with <<<svn mkdir URL>>> for example),
 
     * the plugin works well for multi-module websites publishing to a complete directory:
     you just need to publish <<<mvn site-stage>>> content. But if one module does not publish
-    its ocntent to the same directory (like Surefire or Maven Plugin Tools, which have a
+    its content to the same directory (like Surefire or Enforcer, which have a
     base directory and one plugin in <<</plugins/>>>), this staging area can't be simply imported.
 
     []