[Cocoon Wiki] Update of "CocoonWebsiteUpdate" by VadimGritsenko

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cocoon Wiki" for change notification.

The following page has been changed by VadimGritsenko:
http://wiki.apache.org/cocoon/CocoonWebsiteUpdate

------------------------------------------------------------------------------
  
  ==  A) Checkout Cocoon SVN ==
  
- Checkout the SVN module for the branch that you wish to update:
+ Checkout source for the branch that you wish to update:
-  *  cocoon-1
-  *  cocoon-2.0
-  *  cocoon-2_1_X
+  * CVS module cocoon-1
+  * CVS module cocoon-2.0
+  * SVN url !https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/ into cocoon-2.1
+  * SVN url !https://svn.apache.org/repos/asf/cocoon/trunk/ into cocoon-2.2
  
  If you have checkout already, just update it.
  
  ==  B) Checkout Cocoon Site SVN ==
  
- Checkout cocoon/site SVN module. If you have checkout already, just update it. This repository holds the generated docs for both the top-level website and for each set of version-specific docs. It also holds the source xdocs and the Forrest config files for the top-level website.
+ Checkout SVN url !https://svn.apache.org/repos/asf/cocoon/site/ into site. If you have checkout already, just update it. This repository holds the generated docs for both the top-level website and for each set of version-specific docs. It also holds the source xdocs and the Forrest config files for the top-level website.
  
- Note: cocoon-site is more than 60 Mb. You can checkout only part of it, say, for Cocoon 2.1, cocoon-site/site/2.1 (35Mb)
+ '''NOTE:''' cocoon-site is more than 60 Mb. You can checkout only part of it, say, for Cocoon 2.1, cocoon-site/site/2.1 (35Mb)
+ 
- Note: The javadocs are not stored in the cocoon-site SVN. They can easily be regenerated. Use scp to copy them to the website.
+ '''NOTE:''' The javadocs are not stored in the cocoon-site SVN. They can easily be regenerated. Use scp to copy them to the website.
  
  ==  C) Generate site ==
  
- For the current release branch, e.g. 2.1, this is done by issuing commands 'build docs' followed by 'forrest' in the shell in cocoon-2_1_X root directory.
+ For the current release branch, e.g. 2.1, this is done by issuing commands 'build docs' followed by 'forrest' in the shell in cocoon-2.1 root directory.
  The 'build docs' prepares some additional documents ready for rendering by Forrest.
- After generation is complete, the site will be ready at the build/cocoon-X.Y.Z-dev/site/ directory.
+ After generation is complete, the site will be ready at the build/cocoon-2.1.X-dev/site/ directory.
  
  For the top-level website, just do the command 'forrest' in the top-level cocoon-site directory.
  After generation is complete, the site will be ready at the build/tmp/context/site/ directory.
@@ -42, +44 @@

  ===  Forrest notes ===
  
   * Use Forrest-0.6 (available from the [http://forrest.apache.org/mirrors.cgi#archive Download Archive] and follow its instructions to set FORREST_HOME and PATH environment variables.
-  * Out the box, Forrest will not render PNG images in PDFs (due to license restrictions on Jimi). You need to download Jimi from [http://java.sun.com/products/jimi/ Sun]. Copy the !JimiProClasses.zip file to $FORREST_HOME/lib/optional/jimi-1.0.jar and rebuild Forrest (cd xml-forrest; ./build.sh clean; ./build.sh)
+  * Out of the box, Forrest will not render PNG images in PDFs (due to license restrictions on Jimi). You need to download Jimi from [http://java.sun.com/products/jimi/ Sun]. Copy the !JimiProClasses.zip file to $FORREST_HOME/lib/optional/jimi-1.0.jar and rebuild Forrest (cd xml-forrest; ./build.sh clean; ./build.sh)
  
  We should soon have the [http://forrest.apache.org/ Forrestbot] facility running, which should make all of this vastly simpler.