commons-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject svn commit: r1661745 - /commons/cms-site/trunk/content/xdoc/site-publish.xml
Date Mon, 23 Feb 2015 18:56:18 GMT
Author: sebb
Date: Mon Feb 23 18:56:18 2015
New Revision: 1661745

URL: http://svn.apache.org/r1661745
Log:
Clarify

Modified:
    commons/cms-site/trunk/content/xdoc/site-publish.xml

Modified: commons/cms-site/trunk/content/xdoc/site-publish.xml
URL: http://svn.apache.org/viewvc/commons/cms-site/trunk/content/xdoc/site-publish.xml?rev=1661745&r1=1661744&r2=1661745&view=diff
==============================================================================
--- commons/cms-site/trunk/content/xdoc/site-publish.xml (original)
+++ commons/cms-site/trunk/content/xdoc/site-publish.xml Mon Feb 23 18:56:18 2015
@@ -34,7 +34,7 @@
 
   </section>
   <section name="Main site">
-    <p>The Apache CMS UI can be used to modify and publish main web site: <a href="https://cms.apache.org/commons/">https://cms.apache.org/commons/</a>.
+    <p>The Apache CMS UI can be used to modify and publish the main web site: <a
href="https://cms.apache.org/commons/">https://cms.apache.org/commons/</a>.
       More documentation is available <a href="http://apache.org/dev/cmsref.html">here</a>
 
     </p>
@@ -50,7 +50,9 @@
   </section>
   <section name="Components">
     <p>
-      Components use the maven-scm-publish-plugin. The maven generated site is checked in
to:
+      Components do not use the CMS.
+      Instead component sites need to be built locally and checked in to SVN.
+      The generated site is checked in to:
       <ul>
         <li>proper: https://svn.apache.org/repos/infra/websites/production/commons/content/proper/</li>
         <li>sandbox: https://svn.apache.org/repos/infra/websites/production/commons/content/sandbox/</li>
@@ -60,6 +62,9 @@
     <p>
       Components must use parent 28 (sandbox parent: 10) or later.
     </p>
+    <p>
+    The maven-scm-publish plugin can be used to automatically upload the generated site.
+    </p>
     <p>Maven will create a working copy of the site svn directory (<code>~/commons-sites/</code>
       by default) publish your site to it and commit the changes.  It will not prompt you
for your svn
       password so the commit will fail unless subversion is configured to store your password.
 If it
@@ -72,6 +77,9 @@
     <pre>
       mvn clean site site:stage scm-publish:publish-scm
     </pre>
+    <p>
+    The site can also be built locally and checked into the appropriate location manually.
+    </p>
     <subsection name="Configuration">
       <p>
         Default deployment targets are:



Mime
View raw message