cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From reinh...@apache.org
Subject svn commit: r743862 [1/7] - in /cocoon/site/site: ./ css/ js/
Date Thu, 12 Feb 2009 20:15:44 GMT
Author: reinhard
Date: Thu Feb 12 20:15:42 2009
New Revision: 743862

URL: http://svn.apache.org/viewvc?rev=743862&view=rev
Log:
privacy policy

Added:
    cocoon/site/site/1508_1_1.html   (with props)
Modified:
    cocoon/site/site/1164_1_1.html
    cocoon/site/site/1178_1_1.html
    cocoon/site/site/1199_1_1.html
    cocoon/site/site/1214_1_1.html
    cocoon/site/site/1223_1_1.html
    cocoon/site/site/1256_1_1.html
    cocoon/site/site/1271_1_1.html
    cocoon/site/site/1272_1_1.html
    cocoon/site/site/1273_1_1.html
    cocoon/site/site/1275_1_1.html
    cocoon/site/site/1276_1_1.html
    cocoon/site/site/1277_1_1.html
    cocoon/site/site/1278_1_1.html
    cocoon/site/site/1279_1_1.html
    cocoon/site/site/1281_1_1.html
    cocoon/site/site/1284_1_1.html
    cocoon/site/site/1285_1_1.html
    cocoon/site/site/1286_1_1.html
    cocoon/site/site/1287_1_1.html
    cocoon/site/site/1288_1_1.html
    cocoon/site/site/1289_1_1.html
    cocoon/site/site/1293_1_1.html
    cocoon/site/site/1301_1_1.html
    cocoon/site/site/1302_1_1.html
    cocoon/site/site/1363_1_1.html
    cocoon/site/site/1365_1_1.html
    cocoon/site/site/1368_1_1.html
    cocoon/site/site/1370_1_1.html
    cocoon/site/site/1414_1_1.html
    cocoon/site/site/1416_1_1.html
    cocoon/site/site/1417_1_1.html
    cocoon/site/site/1418_1_1.html
    cocoon/site/site/1421_1_1.html
    cocoon/site/site/1426_1_1.html
    cocoon/site/site/1445_1_1.html
    cocoon/site/site/636_1_1.html
    cocoon/site/site/696_1_1.html
    cocoon/site/site/697_1_1.html
    cocoon/site/site/698_1_1.html
    cocoon/site/site/699_1_1.html
    cocoon/site/site/700_1_1.html
    cocoon/site/site/701_1_1.html
    cocoon/site/site/702_1_1.html
    cocoon/site/site/703_1_1.html
    cocoon/site/site/704_1_1.html
    cocoon/site/site/705_1_1.html
    cocoon/site/site/706_1_1.html
    cocoon/site/site/798_1_1.html
    cocoon/site/site/LICENSE.txt
    cocoon/site/site/NOTICE.txt
    cocoon/site/site/css/site.css
    cocoon/site/site/dependencies.html
    cocoon/site/site/index.html
    cocoon/site/site/integration.html
    cocoon/site/site/issue-tracking.html
    cocoon/site/site/js/getBlank.js
    cocoon/site/site/license.html
    cocoon/site/site/mail-lists.html
    cocoon/site/site/mirror.html
    cocoon/site/site/project-info.html
    cocoon/site/site/project-summary.html
    cocoon/site/site/team-list.html

Modified: cocoon/site/site/1164_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/1164_1_1.html?rev=743862&r1=743861&r2=743862&view=diff
==============================================================================
--- cocoon/site/site/1164_1_1.html (original)
+++ cocoon/site/site/1164_1_1.html Thu Feb 12 20:15:42 2009
@@ -1,388 +1,392 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!--
-  Licensed to the Apache Software Foundation (ASF) under one
-  or more contributor license agreements.  See the NOTICE file
-  distributed with this work for additional information
-  regarding copyright ownership.  The ASF licenses this file
-  to you under the Apache License, Version 2.0 (the
-  "License"); you may not use this file except in compliance
-  with the License.  You may obtain a copy of the License at
-
-   http://www.apache.org/licenses/LICENSE-2.0
-
-  Unless required by applicable law or agreed to in writing,
-  software distributed under the License is distributed on an
-  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-  KIND, either express or implied.  See the License for the
-  specific language governing permissions and limitations
-  under the License.
--->
-
-
-
-
-
-
-
-
-<html>
-  <head>
-    <title>      Cocoon Main Site - How to solve Maven 2 problems
-  </title>
-    <style type="text/css" media="all">
-      @import url("./css/maven-base.css");
-      @import url("./css/maven-theme.css");
-      @import url("./css/site.css");
-    </style>
-    <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
-    <script src="./js/getBlank.js" language="javascript" type="text/javascript"></script>
-          <meta name="author" content="The Cocoon Community" />
-        <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-  </head>
-  <body>
-    <div id="breadtrail">
-       <p><a href="http://www.apache.org">Apache</a> &raquo; <a href="./">Cocoon</a> &raquo;</p>
-    </div>
-    <div id="top">
-      <div id="header">
-          <div class="projectlogo">
-             <a href="./"><img class="logoImage"
-               src="images/cocoon_logo.jpg"
-                alt="Apache Cocoon" border="0" /></a>
-          </div>
-          <div class="grouplogo">
-             <p class="grouptitle"><a href="./">The Apache Cocoon Project</a><img
-               src="images/apache-logo.jpg" alt="Cocoon Project Logo" /></p>
-             <form class="searchbox" action="http://www.google.com/search" method="get">
-               <input value="cocoon.apache.org" name="sitesearch" type="hidden" />
-               <input onFocus="getBlank (this, 'Search the site with google');" size="25" name="q" id="query" type="text" value="Search the site with google" />&nbsp;
-               <input class="searchboxsubmit" name="Search" value="Search" type="submit" />
-             </form>
-         </div>
-         </div>
-         <div id="projectBar">
-           <p class="cocoonHome"><a href="./index.html"><img
-           src="images/pmc-home.gif"
-           alt="  Apache Cocoon
-   homepage"
-           border="0" title="  Apache Cocoon
-   homepage" /></a></p>
-           <h1 class="projectTitle"><a href="./index.html">  Apache Cocoon
-  </a></h1>
-                         <ul class="projectList">
-                <li><strong><a href="./2.2/">Cocoon 2.2</a></em></strong></li>
-                <li><a href="./2.2/core-modules/">Core <span class="pl-version-small">2.2</span></a></li>
-                <li><a href="./2.2/blocks/">Blocks <span class="pl-version-small">2.2</span></a></li>
-                <li><a href="./2.2/maven-plugins/">Maven Plugins <span class="pl-version-small">2.2</span></a></li>
-                <li><strong><a href=".//3.0/">Cocoon 3.0 <span class="pl-version-small">[alpha]</span></a></em></strong></li>            
-                <li><strong><a href="./subprojects/">Subprojects</a></strong></li>
-              </ul>
-                    </div>
-         <div class="projectBarClear"><!-- --></div>
-      </div>
-    <!-- end of top -->
-
-    <div id="content">
-         <ul id="menu">
-        <li>
-              About Cocoon
-            <ul>
-                  
-    <li >
-              <a href="1285_1_1.html">Welcome</a>
-        </li>
-                  
-    <li >
-              <a href="1363_1_1.html">Features</a>
-        </li>
-                  
-    <li >
-              <a href="1284_1_1.html">Versions & Download</a>
-        </li>
-                  
-    <li >
-              <a href="1271_1_1.html">Professional Services</a>
-        </li>
-                  
-  
-
-
-              
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-              
-        <li class='menuCollapse'>
-              <a href="1365_1_1.html">Who uses Cocoon?</a>
-              </li>
-                  
-    <li >
-              <a href="1272_1_1.html">Weblogs</a>
-        </li>
-                  
-    <li >
-              <a href="1178_1_1.html">History</a>
-        </li>
-              </ul>
-    </li>
-      <li>
-              Getting started
-            <ul>
-                  
-    <li >
-              <a href="1370_1_1.html">Tutorials</a>
-        </li>
-              </ul>
-    </li>
-      <li>
-              Getting better
-            <ul>
-                  
-    <li >
-              <a href="1286_1_1.html">About the online documentation</a>
-        </li>
-                  
-    <li >
-              <a href="1287_1_1.html">Presentations</a>
-        </li>
-                  
-    <li >
-              <a href="1368_1_1.html">How-Tos</a>
-        </li>
-                  
-    <li >
-              <a href="1288_1_1.html">Articles</a>
-        </li>
-                  
-    <li >
-              <a href="1289_1_1.html">Books</a>
-        </li>
-              </ul>
-    </li>
-      <li>
-              Getting involved
-            <ul>
-                  
-    <li >
-              <a href="1273_1_1.html">How to contribute?</a>
-        </li>
-                  
-    <li >
-              <a href="1275_1_1.html">Communication tools that we use</a>
-        </li>
-                  
-    <li >
-              <a href="1276_1_1.html">Other tools that we use</a>
-        </li>
-                  
-  
-
-
-              
-      
-            
-      
-            
-      
-            
-            
-                  
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-                    
-            <li class='menuExpand'>
-              <a href="798_1_1.html">Committer's and contributor's section</a>
-                <ul>
-                  
-  
-
-
-              
-      
-            
-      
-            
-            
-              
-            <li class='menuExpand'>
-              <a href="798_1_1.html">Working with Cocoon from SVN</a>
-                <ul>
-                  
-    <li >
-              <a href="798_1_1.html">Building Cocoon 2.2</a>
-        </li>
-                  
-    <li >
-              <a href="1214_1_1.html">How to mount the Cocoon 2.2 projects in Eclipse</a>
-        </li>
-                  
-    <li >
-              <strong>How to solve Maven 2 problems</strong>
-        </li>
-              </ul>
-        </li>
-                  
-    <li >
-              <a href="1301_1_1.html">Debugging Cocoon in  Eclipse</a>
-        </li>
-                  
-    <li >
-              <a href="636_1_1.html">Apache Cocoon Tests</a>
-        </li>
-                  
-    <li >
-              <a href="1199_1_1.html">Releasing Cocoon</a>
-        </li>
-                  
-  
-
-
-              
-      
-            
-      
-            
-      
-              
-        <li class='menuCollapse'>
-              <a href="1418_1_1.html">Documentation</a>
-              </li>
-              </ul>
-        </li>
-              </ul>
-    </li>
-      <li>
-              Project Documentation
-            <ul>
-                  
-  
-
-
-              
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-              
-        <li class='menuCollapse'>
-              <a href="project-info.html">Project Information</a>
-              </li>
-              </ul>
-    </li>
-        <li class="menuVersions">Versions
-      <ul>
-        <li><a href="./3.0/">Cocoon 3.0 <span class="pl-version-small">[alpha]</span></a></li>
-        <li><a href="./2.2/">Cocoon 2.2</a></li>
-        <li><a href="./2.1/">Cocoon 2.1</a></li>
-        <li><a href="./2.0/">Cocoon 2.0</a></li>
-        <li><a href="./1.x/">Cocoon 1.x</a></li>
-      </ul>
-    </li>
-    </ul>
-       <div class="main">
-         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">How to solve Maven 2 problems</h1><p>If you have problems to build Cocoon with Maven 2, please follow these
-instructions. If they don't solve your problem, report your problems to
-<a href="http://issues.apache.org/jira/browse/COCOON">http://issues.apache.org/jira/browse/COCOON</a>.
-An error report should contain your Maven version (<tt>mvn --version</tt>), the
-revision number of you working copy of Cocoon and the complete error report
-(e.g. <tt>mvn install -X -e</tt>).</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Cleanup your local repository</h2><p>It helps to zap your local repo every now and then. There is no way as of yet
-to force maven to redownload poms it has already (MNG-1258).
-Poms<strong> are</strong> being updated without version number increment even
-though they shouldn't. If the problem might exist with Cocoon artifacts only,
-removing [local-maven-repository]/org/apache/cocooon should be enough.</p><p>Maven repository usually is located in the folder:</p><pre>[Win]  C:\Documents and Settings\&lt;Your Login Name&gt;\.m2\repository
-[Unix] ~/.m2/repository
-</pre><p>or different locations can be configured in <tt>~/.m2/settings.xml.</tt></p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Remove a configured Mirror</h2><p>If you're using a mirror (see the section below where to look for the
-configuration) try removing it. The Maven central repository at
-http://repo1.maven.org is the most reliable one and should be fast enough in the
-meantime.</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Configure a mirror</h2><p>Maven relys on public repositories. From time to time they are not accessible
-mostly because of heavy load. To solve this problem, use one of the mirrors in
-<tt>~/.m2/settings.xml</tt>:</p><pre>&lt;settings&gt;
-  &lt;mirrors&gt;
-    &lt;mirror&gt;
-      &lt;mirrorOf&gt;central&lt;/mirrorOf&gt;
-      &lt;id&gt;ibiblioEuropeanMirror&lt;/id&gt;
-      &lt;url&gt;http://mirrors.dotsrc.org/maven2&lt;/url&gt;
-    &lt;/mirror&gt;
-    &lt;!-- 
-    &lt;mirror&gt;
-      &lt;mirrorOf&gt;central&lt;/mirrorOf&gt;
-      &lt;id&gt;ibiblioAustralianMirror&lt;/id&gt;
-      &lt;url&gt;http://public.planetmirror.com/pub/maven2&lt;/url&gt;
-    &lt;/mirror&gt;    
-     --&gt;
-  &lt;/mirrors&gt;
-&lt;/settings&gt;</pre><p>For more information check the page on
-<a href="http://maven.apache.org/guides/mini/guide-mirror-settings.html">configuring
-mirrors</a>.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Common Maven errors</h1><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">java.lang.OutOfMemoryError: Java heap space</h2><p>It occurs when you try whole Cocoon sources, especially
-<a href="2.2/blocks/1.0/1252_1_1.html">serializers block</a>. The problem lays in code of this
-block that demands more than 64mb of memory in order to compile. Solution is
-simple - give Maven more memory by setting environment variable:</p><pre>[Win] set MAVEN_OPTS=-Xmx256m
-[Unix] MAVEN_OPTS='-Xmx256m'
-</pre><p>And then fire your <tt>mvn</tt> command as before. It should work now.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">And when your build works</h1><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Run Maven in offline mode</h2><p>You shouldn't  get any problems anymore as long as you don't update your
-local repo. To switch on the offline mode, append the -o parameter. e.g.</p><pre>mvn clean -o</pre><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Setup a company internal proxy repository</h2><p>If you don't want to rely on external repositories, you can setup a company
-internal <a href="http://maven-proxy.codehaus.org/">proxy repository</a>. The
-Codehaus wiki contains
-<a href="http://docs.codehaus.org/display/MAVENUSER/Creating+a+Maven+proxy">more
-information</a> about the setup process</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
-        us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/1164?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
-      </div></div></div>
-       </div>
-    </div>
-
-    <!-- end of content -->
-    <div id="footer">
-      <p>&#169;  
-          1999-2008
-    
-          The Apache Software Foundation
-      </p>
-    </div>
-    <script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
-    </script>
-    <script type="text/javascript">
-      _uacct = "UA-1740622-3";
-      urchinTracker();
-    </script>
-
-  </body>
-</html>
\ No newline at end of file
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one
+  or more contributor license agreements.  See the NOTICE file
+  distributed with this work for additional information
+  regarding copyright ownership.  The ASF licenses this file
+  to you under the Apache License, Version 2.0 (the
+  "License"); you may not use this file except in compliance
+  with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing,
+  software distributed under the License is distributed on an
+  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+  KIND, either express or implied.  See the License for the
+  specific language governing permissions and limitations
+  under the License.
+-->
+
+
+
+
+
+
+
+
+<html>
+  <head>
+    <title>      Cocoon Main Site - How to solve Maven 2 problems
+  </title>
+    <style type="text/css" media="all">
+      @import url("./css/maven-base.css");
+      @import url("./css/maven-theme.css");
+      @import url("./css/site.css");
+    </style>
+    <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+    <script src="./js/getBlank.js" language="javascript" type="text/javascript"></script>
+          <meta name="author" content="The Cocoon Community" />
+        <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+  </head>
+  <body>
+    <div id="breadtrail">
+       <p><a href="http://www.apache.org">Apache</a> &raquo; <a href="./">Cocoon</a> &raquo;</p>
+    </div>
+    <div id="top">
+      <div id="header">
+          <div class="projectlogo">
+             <a href="./"><img class="logoImage"
+               src="images/cocoon_logo.jpg"
+                alt="Apache Cocoon" border="0" /></a>
+          </div>
+          <div class="grouplogo">
+             <p class="grouptitle"><a href="./">The Apache Cocoon Project</a><img
+               src="images/apache-logo.jpg" alt="Cocoon Project Logo" /></p>
+             <form class="searchbox" action="http://www.google.com/search" method="get">
+               <input value="cocoon.apache.org" name="sitesearch" type="hidden" />
+               <input onFocus="getBlank (this, 'Search the site with google');" size="25" name="q" id="query" type="text" value="Search the site with google" />&nbsp;
+               <input class="searchboxsubmit" name="Search" value="Search" type="submit" />
+             </form>
+         </div>
+         </div>
+         <div id="projectBar">
+           <p class="cocoonHome"><a href="./index.html"><img
+           src="images/pmc-home.gif"
+           alt="  Apache Cocoon
+   homepage"
+           border="0" title="  Apache Cocoon
+   homepage" /></a></p>
+           <h1 class="projectTitle"><a href="./index.html">  Apache Cocoon
+  </a></h1>
+                         <ul class="projectList">
+                <li><strong><a href="./2.2/">Cocoon 2.2</a></em></strong></li>
+                <li><a href="./2.2/core-modules/">Core <span class="pl-version-small">2.2</span></a></li>
+                <li><a href="./2.2/blocks/">Blocks <span class="pl-version-small">2.2</span></a></li>
+                <li><a href="./2.2/maven-plugins/">Maven Plugins <span class="pl-version-small">2.2</span></a></li>
+                <li><strong><a href=".//3.0/">Cocoon 3.0 <span class="pl-version-small">[alpha]</span></a></em></strong></li>            
+                <li><strong><a href="./subprojects/">Subprojects</a></strong></li>
+              </ul>
+                    </div>
+         <div class="projectBarClear"><!-- --></div>
+      </div>
+    <!-- end of top -->
+
+    <div id="content">
+         <ul id="menu">
+        <li>
+              About Cocoon
+            <ul>
+                  
+    <li >
+              <a href="1285_1_1.html">Welcome</a>
+        </li>
+                  
+    <li >
+              <a href="1363_1_1.html">Features</a>
+        </li>
+                  
+    <li >
+              <a href="1284_1_1.html">Versions & Download</a>
+        </li>
+                  
+    <li >
+              <a href="1271_1_1.html">Professional Services</a>
+        </li>
+                  
+  
+
+
+              
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+              
+        <li class='menuCollapse'>
+              <a href="1365_1_1.html">Who uses Cocoon?</a>
+              </li>
+                  
+    <li >
+              <a href="1272_1_1.html">Weblogs</a>
+        </li>
+                  
+    <li >
+              <a href="1178_1_1.html">History</a>
+        </li>
+                  
+    <li >
+              <a href="1508_1_1.html">Privacy Policy</a>
+        </li>
+              </ul>
+    </li>
+      <li>
+              Getting started
+            <ul>
+                  
+    <li >
+              <a href="1370_1_1.html">Tutorials</a>
+        </li>
+              </ul>
+    </li>
+      <li>
+              Getting better
+            <ul>
+                  
+    <li >
+              <a href="1286_1_1.html">About the online documentation</a>
+        </li>
+                  
+    <li >
+              <a href="1287_1_1.html">Presentations</a>
+        </li>
+                  
+    <li >
+              <a href="1368_1_1.html">How-Tos</a>
+        </li>
+                  
+    <li >
+              <a href="1288_1_1.html">Articles</a>
+        </li>
+                  
+    <li >
+              <a href="1289_1_1.html">Books</a>
+        </li>
+              </ul>
+    </li>
+      <li>
+              Getting involved
+            <ul>
+                  
+    <li >
+              <a href="1273_1_1.html">How to contribute?</a>
+        </li>
+                  
+    <li >
+              <a href="1275_1_1.html">Communication tools that we use</a>
+        </li>
+                  
+    <li >
+              <a href="1276_1_1.html">Other tools that we use</a>
+        </li>
+                  
+  
+
+
+              
+      
+            
+      
+            
+      
+            
+            
+                  
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+                    
+            <li class='menuExpand'>
+              <a href="798_1_1.html">Committer's and contributor's section</a>
+                <ul>
+                  
+  
+
+
+              
+      
+            
+      
+            
+            
+              
+            <li class='menuExpand'>
+              <a href="798_1_1.html">Working with Cocoon from SVN</a>
+                <ul>
+                  
+    <li >
+              <a href="798_1_1.html">Building Cocoon 2.2</a>
+        </li>
+                  
+    <li >
+              <a href="1214_1_1.html">How to mount the Cocoon 2.2 projects in Eclipse</a>
+        </li>
+                  
+    <li >
+              <strong>How to solve Maven 2 problems</strong>
+        </li>
+              </ul>
+        </li>
+                  
+    <li >
+              <a href="1301_1_1.html">Debugging Cocoon in  Eclipse</a>
+        </li>
+                  
+    <li >
+              <a href="636_1_1.html">Apache Cocoon Tests</a>
+        </li>
+                  
+    <li >
+              <a href="1199_1_1.html">Releasing Cocoon</a>
+        </li>
+                  
+  
+
+
+              
+      
+            
+      
+            
+      
+              
+        <li class='menuCollapse'>
+              <a href="1418_1_1.html">Documentation</a>
+              </li>
+              </ul>
+        </li>
+              </ul>
+    </li>
+      <li>
+              Project Documentation
+            <ul>
+                  
+  
+
+
+              
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+              
+        <li class='menuCollapse'>
+              <a href="project-info.html">Project Information</a>
+              </li>
+              </ul>
+    </li>
+        <li class="menuVersions">Versions
+      <ul>
+        <li><a href="./3.0/">Cocoon 3.0 <span class="pl-version-small">[alpha]</span></a></li>
+        <li><a href="./2.2/">Cocoon 2.2</a></li>
+        <li><a href="./2.1/">Cocoon 2.1</a></li>
+        <li><a href="./2.0/">Cocoon 2.0</a></li>
+        <li><a href="./1.x/">Cocoon 1.x</a></li>
+      </ul>
+    </li>
+    </ul>
+       <div class="main">
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">How to solve Maven 2 problems</h1><p>If you have problems to build Cocoon with Maven 2, please follow these
+instructions. If they don't solve your problem, report your problems to
+<a href="http://issues.apache.org/jira/browse/COCOON">http://issues.apache.org/jira/browse/COCOON</a>.
+An error report should contain your Maven version (<tt>mvn --version</tt>), the
+revision number of you working copy of Cocoon and the complete error report
+(e.g. <tt>mvn install -X -e</tt>).</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Cleanup your local repository</h2><p>It helps to zap your local repo every now and then. There is no way as of yet
+to force maven to redownload poms it has already (MNG-1258).
+Poms<strong> are</strong> being updated without version number increment even
+though they shouldn't. If the problem might exist with Cocoon artifacts only,
+removing [local-maven-repository]/org/apache/cocooon should be enough.</p><p>Maven repository usually is located in the folder:</p><pre>[Win]  C:\Documents and Settings\&lt;Your Login Name&gt;\.m2\repository
+[Unix] ~/.m2/repository
+</pre><p>or different locations can be configured in <tt>~/.m2/settings.xml.</tt></p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Remove a configured Mirror</h2><p>If you're using a mirror (see the section below where to look for the
+configuration) try removing it. The Maven central repository at
+http://repo1.maven.org is the most reliable one and should be fast enough in the
+meantime.</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Configure a mirror</h2><p>Maven relys on public repositories. From time to time they are not accessible
+mostly because of heavy load. To solve this problem, use one of the mirrors in
+<tt>~/.m2/settings.xml</tt>:</p><pre>&lt;settings&gt;
+  &lt;mirrors&gt;
+    &lt;mirror&gt;
+      &lt;mirrorOf&gt;central&lt;/mirrorOf&gt;
+      &lt;id&gt;ibiblioEuropeanMirror&lt;/id&gt;
+      &lt;url&gt;http://mirrors.dotsrc.org/maven2&lt;/url&gt;
+    &lt;/mirror&gt;
+    &lt;!-- 
+    &lt;mirror&gt;
+      &lt;mirrorOf&gt;central&lt;/mirrorOf&gt;
+      &lt;id&gt;ibiblioAustralianMirror&lt;/id&gt;
+      &lt;url&gt;http://public.planetmirror.com/pub/maven2&lt;/url&gt;
+    &lt;/mirror&gt;    
+     --&gt;
+  &lt;/mirrors&gt;
+&lt;/settings&gt;</pre><p>For more information check the page on
+<a href="http://maven.apache.org/guides/mini/guide-mirror-settings.html">configuring
+mirrors</a>.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Common Maven errors</h1><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">java.lang.OutOfMemoryError: Java heap space</h2><p>It occurs when you try whole Cocoon sources, especially
+<a href="2.2/blocks/1.0/1252_1_1.html">serializers block</a>. The problem lays in code of this
+block that demands more than 64mb of memory in order to compile. Solution is
+simple - give Maven more memory by setting environment variable:</p><pre>[Win] set MAVEN_OPTS=-Xmx256m
+[Unix] MAVEN_OPTS='-Xmx256m'
+</pre><p>And then fire your <tt>mvn</tt> command as before. It should work now.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">And when your build works</h1><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Run Maven in offline mode</h2><p>You shouldn't  get any problems anymore as long as you don't update your
+local repo. To switch on the offline mode, append the -o parameter. e.g.</p><pre>mvn clean -o</pre><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Setup a company internal proxy repository</h2><p>If you don't want to rely on external repositories, you can setup a company
+internal <a href="http://maven-proxy.codehaus.org/">proxy repository</a>. The
+Codehaus wiki contains
+<a href="http://docs.codehaus.org/display/MAVENUSER/Creating+a+Maven+proxy">more
+information</a> about the setup process</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
+        us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/1164?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
+      </div></div></div>
+       </div>
+    </div>
+
+    <!-- end of content -->
+    <div id="footer">
+      <p>&#169;  
+          1999-2009
+    
+          The Apache Software Foundation
+      </p>
+    </div>
+    <script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
+    </script>
+    <script type="text/javascript">
+      _uacct = "UA-1740622-3";
+      urchinTracker();
+    </script>
+
+  </body>
+</html>

Modified: cocoon/site/site/1178_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/1178_1_1.html?rev=743862&r1=743861&r2=743862&view=diff
==============================================================================
--- cocoon/site/site/1178_1_1.html (original)
+++ cocoon/site/site/1178_1_1.html Thu Feb 12 20:15:42 2009
@@ -143,6 +143,10 @@
     <li >
               <strong>History</strong>
         </li>
+                  
+    <li >
+              <a href="1508_1_1.html">Privacy Policy</a>
+        </li>
               </ul>
     </li>
       <li>
@@ -264,7 +268,7 @@
     </li>
     </ul>
        <div class="main">
-         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">History</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">The early years</h1><p>Cocoon started simply enough. In 1998 Jon Stevens -- of Apache JServ,
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">History</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">The early years</h1><p>Cocoon started simply enough. In 1998 Jon Stevens -- of Apache JServ,
 Turbine, Velocity, Anakia, and Tigris Scarab fame -- and I created scripts that
 managed the automatic update of the java.apache.org site. The scripts were dead
 simple: iterate over all the CVS modules that java.apache.org had under the
@@ -312,7 +316,7 @@
 static, some of which may be easier to create by using Cocoon functionalities
 than directly (say, SVG rasterization or applying stylesheets). For example, the
 Cocoon documentation and web site are all generated by Cocoon from the command
-line.</p><p>The history will continue here...</p><p>by Stefano Mazzocchi</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Cocoon 2.1</h1><p>Cocoon 2.1 tried to overcome the flaws of 2.0 and simplify the sitemap.</p><div class="fixme"><div><strong>Fixme: </strong>More overview info here</div></div><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Cocoon 2.2</h1><p>Currently Cocoon 2.2 is under development. Some major changes have happened
+line.</p><p>The history will continue here...</p><p>by Stefano Mazzocchi</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Cocoon 2.1</h1><p>Cocoon 2.1 tried to overcome the flaws of 2.0 and simplify the sitemap.</p><div class="fixme"><div><strong>Fixme: </strong>More overview info here</div></div><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Cocoon 2.2</h1><p>Currently Cocoon 2.2 is under development. Some major changes have happened
 between 2.1 and 2.2: the build process moved from Ant to Maven2 and the
 underlying Avalon framework was replaced by Spring. The change in build system
 also allowed a separation of the Cocoon blocks into separate projects, each with
@@ -325,7 +329,7 @@
     <!-- end of content -->
     <div id="footer">
       <p>&#169;  
-          1999-2008
+          1999-2009
     
           The Apache Software Foundation
       </p>
@@ -338,4 +342,4 @@
     </script>
 
   </body>
-</html>
\ No newline at end of file
+</html>

Modified: cocoon/site/site/1199_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/1199_1_1.html?rev=743862&r1=743861&r2=743862&view=diff
==============================================================================
--- cocoon/site/site/1199_1_1.html (original)
+++ cocoon/site/site/1199_1_1.html Thu Feb 12 20:15:42 2009
@@ -143,6 +143,10 @@
     <li >
               <a href="1178_1_1.html">History</a>
         </li>
+                  
+    <li >
+              <a href="1508_1_1.html">Privacy Policy</a>
+        </li>
               </ul>
     </li>
       <li>
@@ -307,12 +311,12 @@
     </ul>
        <div class="main">
          <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Releasing Cocoon</h1><p>As Cocoon uses Maven 2 as build system, the release process is very simple
-and only requires a few steps.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Step 1: Prepare your workstation</h1><p>In order to get started, you have to make sure that your work station is
-configured correctly:</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Java</h2><p>Make sure that you use Java 1.4. Usually this means setting JAVA_HOME
-correctly.</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">GnuPG</h2><p>Install <a href="http://www.gnupg.org/">GnuPG</a> on your workstation and
+and only requires a few steps.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Step 1: Prepare your workstation</h1><p>In order to get started, you have to make sure that your work station is
+configured correctly:</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Java</h2><p>Make sure that you use Java 1.4. Usually this means setting JAVA_HOME
+correctly.</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">GnuPG</h2><p>Install <a href="http://www.gnupg.org/">GnuPG</a> on your workstation and
 make sure that YOUR key is your default local key. Also add the key to
 <a href="http://svn.apache.org/repos/asf/cocoon/trunk/commons/KEYS">KEYS.</a>
-</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Maven 2</h2><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Unix based systems</h3><ul>
+</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Maven 2</h2><h3 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Unix based systems</h3><ul>
 <li>make sure that you can login to people.apache.org using keys 
 (<a href="http://hacks.oreilly.com/pub/h/66">http://hacks.oreilly.com/pub/h/66</a>)
 </li>
@@ -332,13 +336,13 @@
 &lt;/settings&gt;</pre><div class="note"><div><strong>Note: </strong>Point to an empty local repository. This ensures that you don't
 introduce dependencies that can only be fullfilled within your local build
 environment or after doing the release which puts all created artifacts into
-your local repository.</div></div><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Win32 based systems</h3><div class="fixme"><div><strong>Fixme: </strong>TBD</div></div><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Daisy</h2>It's also a good idea to publish our docs while preparing a release. The
+your local repository.</div></div><h3 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Win32 based systems</h3><div class="fixme"><div><strong>Fixme: </strong>TBD</div></div><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Daisy</h2>It's also a good idea to publish our docs while preparing a release. The
 reason for this is that when a release is created, the information about
 versions (Javadocs, dependencies overview, etc.) exactly reflects the content of
 the released artifact.<br></br>
 For that purpose configure your <tt>settings.xml</tt> as explained in
 <a href="1256_1_1.html">How to build the site locally</a> and give it a dry-run as
-explained in this document before you do the actual release<h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Step 2: Releasing POM artifacts</h1><ol type="1">
+explained in this document before you do the actual release<h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Step 2: Releasing POM artifacts</h1><ol type="1">
 <li>refer to an already released parent in pom.xml</li>
 <li><tt>mvn -N -Dusername=[svn-user-name] -Dpassword=******** release:prepare
 -Darguments=&quot;-N&quot;<br></br>
@@ -353,7 +357,7 @@
 should manually change all poms that have 2-SNAPSHOT for this parent to
 3-SNAPSHOT. Otherwise the trunk build will use &quot;old&quot; ie already released
 artifacts, which is not desired. The pu.sh script in 
-<tt>cocoon/trunk/tools/pom-updater</tt> helps to make the update easier.<h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Step 3: Releasing JAR artifacts</h1><ol type="1">
+<tt>cocoon/trunk/tools/pom-updater</tt> helps to make the update easier.<h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Step 3: Releasing JAR artifacts</h1><ol type="1">
 <li>refer to an already released parent in pom.xml</li>
 <li>replace all SNAPSHOT dependencies with already deployed artifacts</li>
 <li>the dependencies of a POM don't contain version numbers because they are
@@ -387,7 +391,7 @@
 <li>Point all artifacts in trunk to the new snapshot version of this artifact.
 For this purpose update the dependencies management section of the root pom.
 </li>
-</ol><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Additional instructions for special modules</h2><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Multi-module release of Cocoon Core</h3><ul>
+</ol><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Additional instructions for special modules</h2><h3 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Multi-module release of Cocoon Core</h3><ul>
 <li>Before you can invoke a multi-module release of Cocoon core, go to
 <tt>/trunk/core-modules/pom.xml</tt> and enable the dependency management
 section. This has to contain the complete list of all to be released modules.
@@ -397,7 +401,7 @@
 resolve test-jar dependencies from within the release plugin.</li>
 <li>After the release deactivate the dependencyManagement section in
 <tt>/trunk/core-modules/pom.xml </tt>again.</li>
-</ul><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Maven plugin</h3><ul>
+</ul><h3 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Maven plugin</h3><ul>
 <li>Release the <tt>cocoon-rcl-spring-reloader</tt> and the
 <tt>cocoon-rcl-webapp-wrapper</tt> modules first.</li>
 <li>The Maven plugin has two special dependencies that MUSTN'T be declared from
@@ -407,23 +411,23 @@
 and set the constants LIB_VERSION_WRAPPER and LIB_VERSION_SPRING_RELOADER to the
 <em>to-be-released</em> version.</li>
 <li>After the release, set the version to the new SNAPSHOT version.</li>
-</ul><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Step 4: Build Cocoon</h1>The next step is testing whether you have set all dependencies on parent or
+</ul><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Step 4: Build Cocoon</h1>The next step is testing whether you have set all dependencies on parent or
 other modules correctly. The best way to do this is pointing to an empty local
 repository in your ~/.m2/settings.xml file again and do a <tt>mvn install -P
-allblocks</tt> from <tt>./cocoon/trunk</tt>.<h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Step 5: Build the Non-Maven release artifacts</h1>In <tt>cocoon/trunk/tools/release-builder</tt> there is an Ant script that
+allblocks</tt> from <tt>./cocoon/trunk</tt>.<h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Step 5: Build the Non-Maven release artifacts</h1>In <tt>cocoon/trunk/tools/release-builder</tt> there is an Ant script that
 creates release artifacts for blocks, the core, the servlet-service framework
 and the Cocoon configuration project. Read the instructions at the top of the
 script and make sure that your system that builds the artifacts is configured
-properly.<h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Step 6: Call for a vote</h1>Call for a vote that includes information about<ul>
+properly.<h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Step 6: Call for a vote</h1>Call for a vote that includes information about<ul>
 <li>the name and the version of the artifact</li>
 <li>the SVN tag (actually we are voting on SCM tags; we have to trust in the
 release manager that the binaries are generated from the tag)</li>
 <li>how to test it</li>
 <li>time how long the vote will stay open</li>
 <li>pointer to the changes document</li>
-</ul><div class="fixme"><div><strong>Fixme: </strong>Add a mail template here</div></div><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Step 7: Publish the artifacts</h1>If the vote passes, the artifacts are copied to public locations:<h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Maven repository</h2>Copy the artifacts to the Apache sync repository:<pre>cp -R /x1/www/people.apache.org/builds/cocoon/ /x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/
+</ul><div class="fixme"><div><strong>Fixme: </strong>Add a mail template here</div></div><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Step 7: Publish the artifacts</h1>If the vote passes, the artifacts are copied to public locations:<h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Maven repository</h2>Copy the artifacts to the Apache sync repository:<pre>cp -R /x1/www/people.apache.org/builds/cocoon/ /x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/
 </pre>If everything worked fine, you you can delete
-<tt>/x1/www/people.apache.org/builds/cocoon/org</tt>.<h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Apache distribution site</h2>Then copy the distribution artifacts (aka Non-Maven release artifacts):<h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Step 8: Announce the release</h1><div class="fixme"><div><strong>Fixme: </strong>Add a template here</div></div><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Step 9: Update JIRA fields</h1>Cocoon has its own JIRA fields of similar meaing to standard fields
+<tt>/x1/www/people.apache.org/builds/cocoon/org</tt>.<h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Apache distribution site</h2>Then copy the distribution artifacts (aka Non-Maven release artifacts):<h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Step 8: Announce the release</h1><div class="fixme"><div><strong>Fixme: </strong>Add a template here</div></div><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Step 9: Update JIRA fields</h1>Cocoon has its own JIRA fields of similar meaing to standard fields
 <em>Affects Version</em> and <em>Fix version</em> but scoped to one component
 (usually block) only. Administration of these fields can be done only by users
 having JIRA administration rights (project administration rights are not
@@ -443,7 +447,7 @@
 Version in a released POM: 1.0.0-RC2
 Version in the POM file *after* preparing the release: 1.0.0-RC3-SNAPSHOT
 </pre>This will give me (or any other committer if I'm busy) all necessary
-information needed for values update.<h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Tips and tricks</h1><ul>
+information needed for values update.<h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Tips and tricks</h1><ul>
 <li>You can probably omit the username and password if you have committed to the
 cocoon repository before, SVN should have  cached your login credentials.
 (anyway that's how it was for me on Mac OS X)</li>
@@ -454,7 +458,7 @@
 <li>You can reach the staging repository via http at
 <a href="http://people.apache.org/builds/cocoon/">http://people.apache.org/builds/cocoon/</a>
 </li>
-</ul><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">More readings</h1><ul>
+</ul><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">More readings</h1><ul>
 <li>
 <a href="http://maven.apache.org/plugins/maven-release-plugin/">Documentation of
 the Maven release plugin</a></li>
@@ -478,7 +482,7 @@
     <!-- end of content -->
     <div id="footer">
       <p>&#169;  
-          1999-2008
+          1999-2009
     
           The Apache Software Foundation
       </p>
@@ -491,4 +495,4 @@
     </script>
 
   </body>
-</html>
\ No newline at end of file
+</html>

Modified: cocoon/site/site/1214_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/1214_1_1.html?rev=743862&r1=743861&r2=743862&view=diff
==============================================================================
--- cocoon/site/site/1214_1_1.html (original)
+++ cocoon/site/site/1214_1_1.html Thu Feb 12 20:15:42 2009
@@ -143,6 +143,10 @@
     <li >
               <a href="1178_1_1.html">History</a>
         </li>
+                  
+    <li >
+              <a href="1508_1_1.html">Privacy Policy</a>
+        </li>
               </ul>
     </li>
       <li>
@@ -331,7 +335,7 @@
 <tt>/trunk</tt> directory and it should detect the newly created blocks as
 projects.</p><div class="note"><div><strong>Note: </strong>Note that you need to declare the M2_REPO classpath variable in
 your workspace, it should point to your local m2 repository. The Maven eclipse
-plugin offers a goal for this purpose: <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">mvn eclipse:add-maven-repo
+plugin offers a goal for this purpose: <tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">mvn eclipse:add-maven-repo
 -Dworkspace=[path-to-your-local-maven-repo]</tt></div></div><p>You can also get Eclipse to download the sources of dependent libraries and
 attach them to the jars in Eclipse :</p><pre>$ mvn -DdownloadSources=true eclipse:eclipse</pre><p>For further information about the Maven Eclipse plugin visit
 <a href="http://maven.apache.org/plugins/maven-eclipse-plugin/">http://maven.apache.org/plugins/maven-eclipse-plugin/</a>.
@@ -344,7 +348,7 @@
     <!-- end of content -->
     <div id="footer">
       <p>&#169;  
-          1999-2008
+          1999-2009
     
           The Apache Software Foundation
       </p>
@@ -357,4 +361,4 @@
     </script>
 
   </body>
-</html>
\ No newline at end of file
+</html>

Modified: cocoon/site/site/1223_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/1223_1_1.html?rev=743862&r1=743861&r2=743862&view=diff
==============================================================================
--- cocoon/site/site/1223_1_1.html (original)
+++ cocoon/site/site/1223_1_1.html Thu Feb 12 20:15:42 2009
@@ -1,478 +1,482 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!--
-  Licensed to the Apache Software Foundation (ASF) under one
-  or more contributor license agreements.  See the NOTICE file
-  distributed with this work for additional information
-  regarding copyright ownership.  The ASF licenses this file
-  to you under the Apache License, Version 2.0 (the
-  "License"); you may not use this file except in compliance
-  with the License.  You may obtain a copy of the License at
-
-   http://www.apache.org/licenses/LICENSE-2.0
-
-  Unless required by applicable law or agreed to in writing,
-  software distributed under the License is distributed on an
-  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-  KIND, either express or implied.  See the License for the
-  specific language governing permissions and limitations
-  under the License.
--->
-
-
-
-
-
-
-
-
-<html>
-  <head>
-    <title>      Cocoon Main Site - How to create documentation for a deployment unit (e.g. a block)?
-  </title>
-    <style type="text/css" media="all">
-      @import url("./css/maven-base.css");
-      @import url("./css/maven-theme.css");
-      @import url("./css/site.css");
-    </style>
-    <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
-    <script src="./js/getBlank.js" language="javascript" type="text/javascript"></script>
-          <meta name="author" content="The Cocoon Community" />
-        <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-  </head>
-  <body>
-    <div id="breadtrail">
-       <p><a href="http://www.apache.org">Apache</a> &raquo; <a href="./">Cocoon</a> &raquo;</p>
-    </div>
-    <div id="top">
-      <div id="header">
-          <div class="projectlogo">
-             <a href="./"><img class="logoImage"
-               src="images/cocoon_logo.jpg"
-                alt="Apache Cocoon" border="0" /></a>
-          </div>
-          <div class="grouplogo">
-             <p class="grouptitle"><a href="./">The Apache Cocoon Project</a><img
-               src="images/apache-logo.jpg" alt="Cocoon Project Logo" /></p>
-             <form class="searchbox" action="http://www.google.com/search" method="get">
-               <input value="cocoon.apache.org" name="sitesearch" type="hidden" />
-               <input onFocus="getBlank (this, 'Search the site with google');" size="25" name="q" id="query" type="text" value="Search the site with google" />&nbsp;
-               <input class="searchboxsubmit" name="Search" value="Search" type="submit" />
-             </form>
-         </div>
-         </div>
-         <div id="projectBar">
-           <p class="cocoonHome"><a href="./index.html"><img
-           src="images/pmc-home.gif"
-           alt="  Apache Cocoon
-   homepage"
-           border="0" title="  Apache Cocoon
-   homepage" /></a></p>
-           <h1 class="projectTitle"><a href="./index.html">  Apache Cocoon
-  </a></h1>
-                         <ul class="projectList">
-                <li><strong><a href="./2.2/">Cocoon 2.2</a></em></strong></li>
-                <li><a href="./2.2/core-modules/">Core <span class="pl-version-small">2.2</span></a></li>
-                <li><a href="./2.2/blocks/">Blocks <span class="pl-version-small">2.2</span></a></li>
-                <li><a href="./2.2/maven-plugins/">Maven Plugins <span class="pl-version-small">2.2</span></a></li>
-                <li><strong><a href=".//3.0/">Cocoon 3.0 <span class="pl-version-small">[alpha]</span></a></em></strong></li>            
-                <li><strong><a href="./subprojects/">Subprojects</a></strong></li>
-              </ul>
-                    </div>
-         <div class="projectBarClear"><!-- --></div>
-      </div>
-    <!-- end of top -->
-
-    <div id="content">
-         <ul id="menu">
-        <li>
-              About Cocoon
-            <ul>
-                  
-    <li >
-              <a href="1285_1_1.html">Welcome</a>
-        </li>
-                  
-    <li >
-              <a href="1363_1_1.html">Features</a>
-        </li>
-                  
-    <li >
-              <a href="1284_1_1.html">Versions & Download</a>
-        </li>
-                  
-    <li >
-              <a href="1271_1_1.html">Professional Services</a>
-        </li>
-                  
-  
-
-
-              
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-              
-        <li class='menuCollapse'>
-              <a href="1365_1_1.html">Who uses Cocoon?</a>
-              </li>
-                  
-    <li >
-              <a href="1272_1_1.html">Weblogs</a>
-        </li>
-                  
-    <li >
-              <a href="1178_1_1.html">History</a>
-        </li>
-              </ul>
-    </li>
-      <li>
-              Getting started
-            <ul>
-                  
-    <li >
-              <a href="1370_1_1.html">Tutorials</a>
-        </li>
-              </ul>
-    </li>
-      <li>
-              Getting better
-            <ul>
-                  
-    <li >
-              <a href="1286_1_1.html">About the online documentation</a>
-        </li>
-                  
-    <li >
-              <a href="1287_1_1.html">Presentations</a>
-        </li>
-                  
-    <li >
-              <a href="1368_1_1.html">How-Tos</a>
-        </li>
-                  
-    <li >
-              <a href="1288_1_1.html">Articles</a>
-        </li>
-                  
-    <li >
-              <a href="1289_1_1.html">Books</a>
-        </li>
-              </ul>
-    </li>
-      <li>
-              Getting involved
-            <ul>
-                  
-    <li >
-              <a href="1273_1_1.html">How to contribute?</a>
-        </li>
-                  
-    <li >
-              <a href="1275_1_1.html">Communication tools that we use</a>
-        </li>
-                  
-    <li >
-              <a href="1276_1_1.html">Other tools that we use</a>
-        </li>
-                  
-  
-
-
-              
-      
-            
-      
-            
-      
-            
-      
-                  
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-            
-                    
-            <li class='menuExpand'>
-              <a href="798_1_1.html">Committer's and contributor's section</a>
-                <ul>
-                  
-  
-
-
-              
-      
-            
-      
-            
-      
-              
-        <li class='menuCollapse'>
-              <a href="798_1_1.html">Working with Cocoon from SVN</a>
-              </li>
-                  
-    <li >
-              <a href="1301_1_1.html">Debugging Cocoon in  Eclipse</a>
-        </li>
-                  
-    <li >
-              <a href="636_1_1.html">Apache Cocoon Tests</a>
-        </li>
-                  
-    <li >
-              <a href="1199_1_1.html">Releasing Cocoon</a>
-        </li>
-                  
-  
-
-
-              
-      
-            
-      
-            
-            
-              
-            <li class='menuExpand'>
-              <a href="1418_1_1.html">Documentation</a>
-                <ul>
-                  
-    <li >
-              <a href="1418_1_1.html">How to publish docs to cocoon.apache.org</a>
-        </li>
-                  
-    <li >
-              <a href="1256_1_1.html">How to build the site locally</a>
-        </li>
-                  
-    <li >
-              <strong>How to create documentation for a deployment unit (e.g. a block)?</strong>
-        </li>
-              </ul>
-        </li>
-              </ul>
-        </li>
-              </ul>
-    </li>
-      <li>
-              Project Documentation
-            <ul>
-                  
-  
-
-
-              
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-            
-      
-              
-        <li class='menuCollapse'>
-              <a href="project-info.html">Project Information</a>
-              </li>
-              </ul>
-    </li>
-        <li class="menuVersions">Versions
-      <ul>
-        <li><a href="./3.0/">Cocoon 3.0 <span class="pl-version-small">[alpha]</span></a></li>
-        <li><a href="./2.2/">Cocoon 2.2</a></li>
-        <li><a href="./2.1/">Cocoon 2.1</a></li>
-        <li><a href="./2.0/">Cocoon 2.0</a></li>
-        <li><a href="./1.x/">Cocoon 1.x</a></li>
-      </ul>
-    </li>
-    </ul>
-       <div class="main">
-         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">How to create documentation for a deployment unit (e.g. a block)?</h1><p>In Cocoon 2.2 each block has its own release cycle and also its own
-documentation set. This set is created through a separate site in Daisy. Each
-set has its own collection which is used by the Daisy export plugin in Maven to
-build the complete site, either locally at your hard disk, or at the official
-site.</p><p>The following steps outline the process to go through to create a block site.
-As an example we use the CForms block.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Create the collection</h1><p>In Daisy, open Administration -&gt; Manage collections.<br></br>
-Add a new collection for the block. The name should be
-<tt>cdocs-blockname</tt>, where <tt>blockname</tt> is the part of the name of
-the block after cocoon. Example: when the block is named <tt>cocoon-forms</tt>,
-the name of the collection should be <em>cdocs-forms</em>. <br></br>
-Note the id of the collection (in this case <em>7</em>).</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Create the navigation document</h1><p>Each block has its own navigation document, which simplifies the packaging of
-the documation strictly for that block.</p><ol type="1">
-<li>In Daisy, create a New Document and choose type <tt>Book Definition</tt>.
-</li>
-<li>Set the name of the document to <tt>&lt;user friendly name&gt; Block
-[navigation]</tt>. For the CForms block that would be <em>Forms Block
-[navigation]</em>.</li>
-<li>Go to the Misc tab and add the proper collection, in this case cdocs-forms.
-</li>
-<li>Underneath the root, add the toplevel folder for this block, by adding a new
-section node. Set the title to a user friendly name of the block. For the CForms
-block that would be <em>Forms</em>.</li>
-<li>Underneath this folder, add two documents, one is called
-<strong>Introduction</strong>, one is called <strong>Samples</strong>. You can
-create the documents by adding a new section node, and then select the &quot;link to
-new document&quot; button (second button after the document ID). Make sure these
-documents are also part of the proper collection, i.e. the
-<em>cdocs-forms</em>.</li>
-<li>Publish the document (mark a checkbox 'Publish changes immediately').</li>
-</ol>Note the id of the navigation document (in this case <em>1152</em>).<h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Create a new Daisy site</h1>Each block gets its own site in Daisy. Before adding documentation about the
-block, the site should be selected. This way all documents will automatically be
-in the proper collection.The steps below describe how to create a new Daisy site.<ol type="1">
-<li>Log in to cocoon.zones.apache.org with your username and password</li>
-<li>change to user daisy: <tt>sudo su - daisy</tt></li>
-<li><tt>cd daisywikidata/sites</tt></li>
-<li>copy another block to the new block with blockname equal to the collection
-name. Example: <tt>cp -R cdocs-fop cdocs-forms</tt></li>
-<li>cd into the new folder: <tt>cd cdocs-forms</tt></li>
-<li>modify the siteconf.xml file:
-<ul>
-<li>change the <tt>title</tt> to match the name of the navigation document
-(without the [navigation] part), e.g. <em>Forms Block</em></li>
-<li>change the <tt>description</tt> to match the block name, e.g.<em>
-Documentation of the Forms Block<br></br>
-</em></li>
-<li>change the <tt>navigationDocId</tt> to the id of the navigation document (in
-this case <em>1152</em>)</li>
-<li>change the <tt>homepageDocId</tt> to the id of the introduction document (in
-this case <em>489</em>)</li>
-<li>change the <tt>collectionId</tt> to the id of the new collection (in this
-case <em>7</em>)</li>
-</ul>
-</li>
-<li>save the file and logout of the server.</li>
-</ol><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Add the navigation to the master navigation file</h1>To show the block documentation in the total Cocoon documentation site, which
-is the source for the official documentation, you need to add the navigation
-document to the master navigation file. Do this step <strong>after</strong>
-creating the site, as a reminder that the site should be created as well.<br></br>
-These are the steps to take:<ol type="1">
-<li>In Daisy, go to the <tt>cdocs: Apache Cocoon</tt> site</li>
-<li>Select <tt>Administration</tt> in the <em>navigation menu</em> (so not on
-top!!!)</li>
-<li>You should now see a tree that represents the navigation tree of the cdocs
-site. This page is here only to provide convenient links to all the navigation
-documents.</li>
-<li>Edit the document to add the links to the navigation document. Make sure the
-block names are in alphabetical order and reflect the actual menu hierarchy.
-</li>
-<li>Save the document and select the <tt>Cocoon Book</tt> link.</li>
-<li>Edit the navigation document and add a <tt>new import navigation node</tt>
-with the id of the navigation document (in this case <em>1152</em>)</li>
-</ol><div class="note"><div><strong>Note: </strong>When adding documentation for the block, be sure you select the
-proper site first!</div></div><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Configuring the Maven pom files</h1>With the Daisy Maven plugin the information can be extracted from Daisy and
-built into the official site, either locally or at the official Cocoon
-documentation site.The steps below configure the Maven pom files to make this happen.<h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Configure the root pom.xml</h2>Create two properties in trunk/parent/pom.xml. This is makes it easier to
-maintain these two pieces of information throughout the documentation generation
-process:<pre>&lt;properties&gt;
-  [...] 
-  &lt;docs.m.forms.version&gt;1.0&lt;/docs.m.forms.version&gt;
-  &lt;docs.m.forms.relPath&gt;blocks/forms/${docs.m.forms.version}/&lt;/docs.m.forms.relPath&gt;     
-&lt;/properties&gt;
-</pre>Open the pom.xml in the root and find the plugin with artifactId
-daisy-maven-plugin. Under <tt>collections</tt> add<pre> &lt;collection&gt;
-    &lt;name&gt;cdocs-forms&lt;/name&gt;
-    &lt;path&gt;${docs.m.forms.relPath}&lt;/path&gt;
-  &lt;/collection&gt;</pre>Try to keep the collections in alphabetical order as well.<h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Configure the block pom.xml</h2><ul>
-<li>Open the <tt>pom.xml</tt> file of the block, e.g.
-<em>cocoon-forms-impl/pom.xml</em></li>
-<li>Open a pom.xml file of a block that is already configured, e.g. cocoon-fop
-and copy the plugin with the groupID <tt>org.daisycms </tt>and artifactId<tt>
-daisy-maven-plugin</tt></li>
-<li>Add this to your pom file under &lt;build&gt;, &lt;plugins&gt;, if necessary
-create these tags. The build section should look like this (at least containing
-the daisy-maven-plugin part)</li>
-</ul><ol type="1"> 
-</ol><pre>    &lt;build&gt;
-        &lt;plugins&gt;
-            &lt;plugin&gt;
-                &lt;groupId&gt;org.daisycms&lt;/groupId&gt;
-                &lt;artifactId&gt;daisy-maven-plugin&lt;/artifactId&gt;
-                &lt;configuration&gt;
-                    &lt;navDocId&gt;1152&lt;/navDocId&gt;
-                    &lt;collection&gt;cdocs-forms&lt;/collection&gt;                   
-                    &lt;skipFirstNavigationDocumentLevel&gt;true&lt;/skipFirstNavigationDocumentLevel&gt;
-                &lt;/configuration&gt;
-            &lt;/plugin&gt;
-        &lt;/plugins&gt;
-    &lt;/build&gt;</pre><ul>
-<li>Change the <tt>navDocId</tt> to the id of the navigation document, in this
-case <em>1152</em></li>
-<li>Change the <tt>collection</tt> to the name of the collection, in this case
-<em>cdocs-forms</em></li>
-<li>Add the distributionManagment part and the properties as well at the same
-level as the build tag.</li>
-</ul><pre>  &lt;distributionManagement&gt;
-    &lt;site&gt;
-      &lt;id&gt;website&lt;/id&gt;
-      &lt;url&gt;${docs.deploymentBaseUrl}/${docs.m.forms.relPath}&lt;/url&gt;
-    &lt;/site&gt;
-  &lt;/distributionManagement&gt;
-  &lt;properties&gt;
-    &lt;docs.name&gt;<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Cocoon Forms</strong>&lt;/docs.name&gt;    
-    &lt;docs.version&gt;${docs.m.forms.version}&lt;/docs.version&gt;
-  &lt;/properties&gt;
-</pre><ul>
-<li>Change the path in the <tt>url</tt> to match the block name, here
-<em>forms</em></li>
-<li>Change the property <tt>docs.name</tt> to match the user friendly name of
-the block, here <em>Cocoon Forms</em></li>
-<li>Set the <tt>docs.version</tt> property to 1.0 initially and update it to
-reflect the documentation version.</li>
-</ul><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Configure the site pom.xml</h2>Open the pom.xml in the site and add a module to the section Cocoon Blocks:
-<pre>    &lt;module&gt;../blocks/cocoon-forms/cocoon-forms-impl&lt;/module&gt;
-</pre>Keep the modules in alphabetical order to ease maintenance.</div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
-        us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/1223?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
-      </div></div></div>
-       </div>
-    </div>
-
-    <!-- end of content -->
-    <div id="footer">
-      <p>&#169;  
-          1999-2008
-    
-          The Apache Software Foundation
-      </p>
-    </div>
-    <script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
-    </script>
-    <script type="text/javascript">
-      _uacct = "UA-1740622-3";
-      urchinTracker();
-    </script>
-
-  </body>
-</html>
\ No newline at end of file
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one
+  or more contributor license agreements.  See the NOTICE file
+  distributed with this work for additional information
+  regarding copyright ownership.  The ASF licenses this file
+  to you under the Apache License, Version 2.0 (the
+  "License"); you may not use this file except in compliance
+  with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing,
+  software distributed under the License is distributed on an
+  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+  KIND, either express or implied.  See the License for the
+  specific language governing permissions and limitations
+  under the License.
+-->
+
+
+
+
+
+
+
+
+<html>
+  <head>
+    <title>      Cocoon Main Site - How to create documentation for a deployment unit (e.g. a block)?
+  </title>
+    <style type="text/css" media="all">
+      @import url("./css/maven-base.css");
+      @import url("./css/maven-theme.css");
+      @import url("./css/site.css");
+    </style>
+    <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+    <script src="./js/getBlank.js" language="javascript" type="text/javascript"></script>
+          <meta name="author" content="The Cocoon Community" />
+        <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+  </head>
+  <body>
+    <div id="breadtrail">
+       <p><a href="http://www.apache.org">Apache</a> &raquo; <a href="./">Cocoon</a> &raquo;</p>
+    </div>
+    <div id="top">
+      <div id="header">
+          <div class="projectlogo">
+             <a href="./"><img class="logoImage"
+               src="images/cocoon_logo.jpg"
+                alt="Apache Cocoon" border="0" /></a>
+          </div>
+          <div class="grouplogo">
+             <p class="grouptitle"><a href="./">The Apache Cocoon Project</a><img
+               src="images/apache-logo.jpg" alt="Cocoon Project Logo" /></p>
+             <form class="searchbox" action="http://www.google.com/search" method="get">
+               <input value="cocoon.apache.org" name="sitesearch" type="hidden" />
+               <input onFocus="getBlank (this, 'Search the site with google');" size="25" name="q" id="query" type="text" value="Search the site with google" />&nbsp;
+               <input class="searchboxsubmit" name="Search" value="Search" type="submit" />
+             </form>
+         </div>
+         </div>
+         <div id="projectBar">
+           <p class="cocoonHome"><a href="./index.html"><img
+           src="images/pmc-home.gif"
+           alt="  Apache Cocoon
+   homepage"
+           border="0" title="  Apache Cocoon
+   homepage" /></a></p>
+           <h1 class="projectTitle"><a href="./index.html">  Apache Cocoon
+  </a></h1>
+                         <ul class="projectList">
+                <li><strong><a href="./2.2/">Cocoon 2.2</a></em></strong></li>
+                <li><a href="./2.2/core-modules/">Core <span class="pl-version-small">2.2</span></a></li>
+                <li><a href="./2.2/blocks/">Blocks <span class="pl-version-small">2.2</span></a></li>
+                <li><a href="./2.2/maven-plugins/">Maven Plugins <span class="pl-version-small">2.2</span></a></li>
+                <li><strong><a href=".//3.0/">Cocoon 3.0 <span class="pl-version-small">[alpha]</span></a></em></strong></li>            
+                <li><strong><a href="./subprojects/">Subprojects</a></strong></li>
+              </ul>
+                    </div>
+         <div class="projectBarClear"><!-- --></div>
+      </div>
+    <!-- end of top -->
+
+    <div id="content">
+         <ul id="menu">
+        <li>
+              About Cocoon
+            <ul>
+                  
+    <li >
+              <a href="1285_1_1.html">Welcome</a>
+        </li>
+                  
+    <li >
+              <a href="1363_1_1.html">Features</a>
+        </li>
+                  
+    <li >
+              <a href="1284_1_1.html">Versions & Download</a>
+        </li>
+                  
+    <li >
+              <a href="1271_1_1.html">Professional Services</a>
+        </li>
+                  
+  
+
+
+              
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+              
+        <li class='menuCollapse'>
+              <a href="1365_1_1.html">Who uses Cocoon?</a>
+              </li>
+                  
+    <li >
+              <a href="1272_1_1.html">Weblogs</a>
+        </li>
+                  
+    <li >
+              <a href="1178_1_1.html">History</a>
+        </li>
+                  
+    <li >
+              <a href="1508_1_1.html">Privacy Policy</a>
+        </li>
+              </ul>
+    </li>
+      <li>
+              Getting started
+            <ul>
+                  
+    <li >
+              <a href="1370_1_1.html">Tutorials</a>
+        </li>
+              </ul>
+    </li>
+      <li>
+              Getting better
+            <ul>
+                  
+    <li >
+              <a href="1286_1_1.html">About the online documentation</a>
+        </li>
+                  
+    <li >
+              <a href="1287_1_1.html">Presentations</a>
+        </li>
+                  
+    <li >
+              <a href="1368_1_1.html">How-Tos</a>
+        </li>
+                  
+    <li >
+              <a href="1288_1_1.html">Articles</a>
+        </li>
+                  
+    <li >
+              <a href="1289_1_1.html">Books</a>
+        </li>
+              </ul>
+    </li>
+      <li>
+              Getting involved
+            <ul>
+                  
+    <li >
+              <a href="1273_1_1.html">How to contribute?</a>
+        </li>
+                  
+    <li >
+              <a href="1275_1_1.html">Communication tools that we use</a>
+        </li>
+                  
+    <li >
+              <a href="1276_1_1.html">Other tools that we use</a>
+        </li>
+                  
+  
+
+
+              
+      
+            
+      
+            
+      
+            
+      
+                  
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+            
+                    
+            <li class='menuExpand'>
+              <a href="798_1_1.html">Committer's and contributor's section</a>
+                <ul>
+                  
+  
+
+
+              
+      
+            
+      
+            
+      
+              
+        <li class='menuCollapse'>
+              <a href="798_1_1.html">Working with Cocoon from SVN</a>
+              </li>
+                  
+    <li >
+              <a href="1301_1_1.html">Debugging Cocoon in  Eclipse</a>
+        </li>
+                  
+    <li >
+              <a href="636_1_1.html">Apache Cocoon Tests</a>
+        </li>
+                  
+    <li >
+              <a href="1199_1_1.html">Releasing Cocoon</a>
+        </li>
+                  
+  
+
+
+              
+      
+            
+      
+            
+            
+              
+            <li class='menuExpand'>
+              <a href="1418_1_1.html">Documentation</a>
+                <ul>
+                  
+    <li >
+              <a href="1418_1_1.html">How to publish docs to cocoon.apache.org</a>
+        </li>
+                  
+    <li >
+              <a href="1256_1_1.html">How to build the site locally</a>
+        </li>
+                  
+    <li >
+              <strong>How to create documentation for a deployment unit (e.g. a block)?</strong>
+        </li>
+              </ul>
+        </li>
+              </ul>
+        </li>
+              </ul>
+    </li>
+      <li>
+              Project Documentation
+            <ul>
+                  
+  
+
+
+              
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+            
+      
+              
+        <li class='menuCollapse'>
+              <a href="project-info.html">Project Information</a>
+              </li>
+              </ul>
+    </li>
+        <li class="menuVersions">Versions
+      <ul>
+        <li><a href="./3.0/">Cocoon 3.0 <span class="pl-version-small">[alpha]</span></a></li>
+        <li><a href="./2.2/">Cocoon 2.2</a></li>
+        <li><a href="./2.1/">Cocoon 2.1</a></li>
+        <li><a href="./2.0/">Cocoon 2.0</a></li>
+        <li><a href="./1.x/">Cocoon 1.x</a></li>
+      </ul>
+    </li>
+    </ul>
+       <div class="main">
+         <div id="contentBody"><div id="bodyText"><h1 class="docTitle">How to create documentation for a deployment unit (e.g. a block)?</h1><p>In Cocoon 2.2 each block has its own release cycle and also its own
+documentation set. This set is created through a separate site in Daisy. Each
+set has its own collection which is used by the Daisy export plugin in Maven to
+build the complete site, either locally at your hard disk, or at the official
+site.</p><p>The following steps outline the process to go through to create a block site.
+As an example we use the CForms block.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Create the collection</h1><p>In Daisy, open Administration -&gt; Manage collections.<br></br>
+Add a new collection for the block. The name should be
+<tt>cdocs-blockname</tt>, where <tt>blockname</tt> is the part of the name of
+the block after cocoon. Example: when the block is named <tt>cocoon-forms</tt>,
+the name of the collection should be <em>cdocs-forms</em>. <br></br>
+Note the id of the collection (in this case <em>7</em>).</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Create the navigation document</h1><p>Each block has its own navigation document, which simplifies the packaging of
+the documation strictly for that block.</p><ol type="1">
+<li>In Daisy, create a New Document and choose type <tt>Book Definition</tt>.
+</li>
+<li>Set the name of the document to <tt>&lt;user friendly name&gt; Block
+[navigation]</tt>. For the CForms block that would be <em>Forms Block
+[navigation]</em>.</li>
+<li>Go to the Misc tab and add the proper collection, in this case cdocs-forms.
+</li>
+<li>Underneath the root, add the toplevel folder for this block, by adding a new
+section node. Set the title to a user friendly name of the block. For the CForms
+block that would be <em>Forms</em>.</li>
+<li>Underneath this folder, add two documents, one is called
+<strong>Introduction</strong>, one is called <strong>Samples</strong>. You can
+create the documents by adding a new section node, and then select the &quot;link to
+new document&quot; button (second button after the document ID). Make sure these
+documents are also part of the proper collection, i.e. the
+<em>cdocs-forms</em>.</li>
+<li>Publish the document (mark a checkbox 'Publish changes immediately').</li>
+</ol>Note the id of the navigation document (in this case <em>1152</em>).<h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Create a new Daisy site</h1>Each block gets its own site in Daisy. Before adding documentation about the
+block, the site should be selected. This way all documents will automatically be
+in the proper collection.The steps below describe how to create a new Daisy site.<ol type="1">
+<li>Log in to cocoon.zones.apache.org with your username and password</li>
+<li>change to user daisy: <tt>sudo su - daisy</tt></li>
+<li><tt>cd daisywikidata/sites</tt></li>
+<li>copy another block to the new block with blockname equal to the collection
+name. Example: <tt>cp -R cdocs-fop cdocs-forms</tt></li>
+<li>cd into the new folder: <tt>cd cdocs-forms</tt></li>
+<li>modify the siteconf.xml file:
+<ul>
+<li>change the <tt>title</tt> to match the name of the navigation document
+(without the [navigation] part), e.g. <em>Forms Block</em></li>
+<li>change the <tt>description</tt> to match the block name, e.g.<em>
+Documentation of the Forms Block<br></br>
+</em></li>
+<li>change the <tt>navigationDocId</tt> to the id of the navigation document (in
+this case <em>1152</em>)</li>
+<li>change the <tt>homepageDocId</tt> to the id of the introduction document (in
+this case <em>489</em>)</li>
+<li>change the <tt>collectionId</tt> to the id of the new collection (in this
+case <em>7</em>)</li>
+</ul>
+</li>
+<li>save the file and logout of the server.</li>
+</ol><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Add the navigation to the master navigation file</h1>To show the block documentation in the total Cocoon documentation site, which
+is the source for the official documentation, you need to add the navigation
+document to the master navigation file. Do this step <strong>after</strong>
+creating the site, as a reminder that the site should be created as well.<br></br>
+These are the steps to take:<ol type="1">
+<li>In Daisy, go to the <tt>cdocs: Apache Cocoon</tt> site</li>
+<li>Select <tt>Administration</tt> in the <em>navigation menu</em> (so not on
+top!!!)</li>
+<li>You should now see a tree that represents the navigation tree of the cdocs
+site. This page is here only to provide convenient links to all the navigation
+documents.</li>
+<li>Edit the document to add the links to the navigation document. Make sure the
+block names are in alphabetical order and reflect the actual menu hierarchy.
+</li>
+<li>Save the document and select the <tt>Cocoon Book</tt> link.</li>
+<li>Edit the navigation document and add a <tt>new import navigation node</tt>
+with the id of the navigation document (in this case <em>1152</em>)</li>
+</ol><div class="note"><div><strong>Note: </strong>When adding documentation for the block, be sure you select the
+proper site first!</div></div><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Configuring the Maven pom files</h1>With the Daisy Maven plugin the information can be extracted from Daisy and
+built into the official site, either locally or at the official Cocoon
+documentation site.The steps below configure the Maven pom files to make this happen.<h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Configure the root pom.xml</h2>Create two properties in trunk/parent/pom.xml. This is makes it easier to
+maintain these two pieces of information throughout the documentation generation
+process:<pre>&lt;properties&gt;
+  [...] 
+  &lt;docs.m.forms.version&gt;1.0&lt;/docs.m.forms.version&gt;
+  &lt;docs.m.forms.relPath&gt;blocks/forms/${docs.m.forms.version}/&lt;/docs.m.forms.relPath&gt;     
+&lt;/properties&gt;
+</pre>Open the pom.xml in the root and find the plugin with artifactId
+daisy-maven-plugin. Under <tt>collections</tt> add<pre> &lt;collection&gt;
+    &lt;name&gt;cdocs-forms&lt;/name&gt;
+    &lt;path&gt;${docs.m.forms.relPath}&lt;/path&gt;
+  &lt;/collection&gt;</pre>Try to keep the collections in alphabetical order as well.<h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Configure the block pom.xml</h2><ul>
+<li>Open the <tt>pom.xml</tt> file of the block, e.g.
+<em>cocoon-forms-impl/pom.xml</em></li>
+<li>Open a pom.xml file of a block that is already configured, e.g. cocoon-fop
+and copy the plugin with the groupID <tt>org.daisycms </tt>and artifactId<tt>
+daisy-maven-plugin</tt></li>
+<li>Add this to your pom file under &lt;build&gt;, &lt;plugins&gt;, if necessary
+create these tags. The build section should look like this (at least containing
+the daisy-maven-plugin part)</li>
+</ul><ol type="1"> 
+</ol><pre>    &lt;build&gt;
+        &lt;plugins&gt;
+            &lt;plugin&gt;
+                &lt;groupId&gt;org.daisycms&lt;/groupId&gt;
+                &lt;artifactId&gt;daisy-maven-plugin&lt;/artifactId&gt;
+                &lt;configuration&gt;
+                    &lt;navDocId&gt;1152&lt;/navDocId&gt;
+                    &lt;collection&gt;cdocs-forms&lt;/collection&gt;                   
+                    &lt;skipFirstNavigationDocumentLevel&gt;true&lt;/skipFirstNavigationDocumentLevel&gt;
+                &lt;/configuration&gt;
+            &lt;/plugin&gt;
+        &lt;/plugins&gt;
+    &lt;/build&gt;</pre><ul>
+<li>Change the <tt>navDocId</tt> to the id of the navigation document, in this
+case <em>1152</em></li>
+<li>Change the <tt>collection</tt> to the name of the collection, in this case
+<em>cdocs-forms</em></li>
+<li>Add the distributionManagment part and the properties as well at the same
+level as the build tag.</li>
+</ul><pre>  &lt;distributionManagement&gt;
+    &lt;site&gt;
+      &lt;id&gt;website&lt;/id&gt;
+      &lt;url&gt;${docs.deploymentBaseUrl}/${docs.m.forms.relPath}&lt;/url&gt;
+    &lt;/site&gt;
+  &lt;/distributionManagement&gt;
+  &lt;properties&gt;
+    &lt;docs.name&gt;<strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Cocoon Forms</strong>&lt;/docs.name&gt;    
+    &lt;docs.version&gt;${docs.m.forms.version}&lt;/docs.version&gt;
+  &lt;/properties&gt;
+</pre><ul>
+<li>Change the path in the <tt>url</tt> to match the block name, here
+<em>forms</em></li>
+<li>Change the property <tt>docs.name</tt> to match the user friendly name of
+the block, here <em>Cocoon Forms</em></li>
+<li>Set the <tt>docs.version</tt> property to 1.0 initially and update it to
+reflect the documentation version.</li>
+</ul><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Configure the site pom.xml</h2>Open the pom.xml in the site and add a module to the section Cocoon Blocks:
+<pre>    &lt;module&gt;../blocks/cocoon-forms/cocoon-forms-impl&lt;/module&gt;
+</pre>Keep the modules in alphabetical order to ease maintenance.</div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
+        us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/1223?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
+      </div></div></div>
+       </div>
+    </div>
+
+    <!-- end of content -->
+    <div id="footer">
+      <p>&#169;  
+          1999-2009
+    
+          The Apache Software Foundation
+      </p>
+    </div>
+    <script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
+    </script>
+    <script type="text/javascript">
+      _uacct = "UA-1740622-3";
+      urchinTracker();
+    </script>
+
+  </body>
+</html>



Mime
View raw message