You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@turbine.apache.org by gk...@apache.org on 2014/02/26 23:29:14 UTC

svn commit: r1572304 - /turbine/fulcrum/trunk/security/README

Author: gk
Date: Wed Feb 26 22:29:14 2014
New Revision: 1572304

URL: http://svn.apache.org/r1572304
Log:
Update README (scm publishing fpr master modules)

Modified:
    turbine/fulcrum/trunk/security/README

Modified: turbine/fulcrum/trunk/security/README
URL: http://svn.apache.org/viewvc/turbine/fulcrum/trunk/security/README?rev=1572304&r1=1572303&r2=1572304&view=diff
==============================================================================
--- turbine/fulcrum/trunk/security/README (original)
+++ turbine/fulcrum/trunk/security/README Wed Feb 26 22:29:14 2014
@@ -1,6 +1,6 @@
 $Id$
 
-The Fulcrum Website Instructions
+The Fulcrum Website Instructions for Multi Modules
 --------------------------------
 
 The Fulcrum web site is based on .xml files which are transformed
@@ -14,13 +14,9 @@ Using scm-publish Plugin, cft. http://co
 
 * Verify turbine.scmPubCheckoutDirectory is matching property checkoutDirectory of goal scm-publish:publish-scm.
 
-* Once you have the site checked out locally, cd into your fulcrum-site directory and execute, if single project
+* Once you have the site checked out locally, as it is multi-module project (with submodules) execute
 
-  mvn site 
-
-  or if it is multi-module project (with submodules)
-
-  mvn site:stage
+  mvn site site:stage
 
 This will build the documentation into the target/site/, resp. target/staging/ directory. The output will show you which files got re-generated.
 
@@ -30,10 +26,10 @@ This will build the documentation into t
 
 * To test what files would be added, deleted or updated run:
 
-  mvn site:stage scm-publish:publish-scm -Dscmpublish.dryRun=true
+  mvn site site:stage scm-publish:publish-scm -Dscmpublish.dryRun=true
 
-This prints any changes to STDOUT. 
+This will generate the site into turbine.site.cache folder (target/turbine-sites by default) and print any changes to STDOUT. 
 
-* To deploy run (add -Dusername=<username> -Dpassword=<pw>) remove scmpublish.dryRun or set to false. Check if tryUpdate is set to false to get a clean working copy again). Alternatively, if you have set scmpublish.skipCheckin=true in the previous step, you have to do a manual commit. 
+* To deploy run the same command adding -Dusername=<username> -Dpassword=<pw> and remove the argument scmpublish.dryRun or set it to false. Check if tryUpdate is set to false to get a clean working copy again). Alternatively, if you have set scmpublish.skipCheckin=true in the previous step, you have to do a manual commit.