Author: ilgrosso
Date: Tue Apr 10 10:20:04 2012
New Revision: 1311664
URL: http://svn.apache.org/viewvc?rev=1311664&view=rev
Log:
Maven site re-generation from existing published HTML files (main site)
Added:
cocoon/trunk/site/cocoon-main-site/src/site/
cocoon/trunk/site/cocoon-main-site/src/site/resources/
cocoon/trunk/site/cocoon-main-site/src/site/resources/images/
cocoon/trunk/site/cocoon-main-site/src/site/resources/images/external.png (with props)
cocoon/trunk/site/cocoon-main-site/src/site/site.xml
- copied, changed from r1311155, cocoon/cocoon3/trunk/parent/src/site/site.xml
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1164_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1178_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1199_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1214_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1223_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1256_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1271_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1272_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1273_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1275_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1276_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1277_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1278_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1279_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1281_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1284_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1286_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1287_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1288_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1289_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1293_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1301_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1302_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1363_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1365_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1368_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1370_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1414_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1416_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1417_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1418_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1421_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1426_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1445_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1487_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1508_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/636_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/696_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/697_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/698_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/699_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/700_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/701_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/702_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/703_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/704_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/705_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/706_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/798_1_1.xml (with props)
cocoon/trunk/site/cocoon-main-site/src/site/xdoc/index.xml (with props)
Modified:
cocoon/trunk/site/cocoon-main-site/pom.xml
Modified: cocoon/trunk/site/cocoon-main-site/pom.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-main-site/pom.xml?rev=1311664&r1=1311663&r2=1311664&view=diff
==============================================================================
--- cocoon/trunk/site/cocoon-main-site/pom.xml (original)
+++ cocoon/trunk/site/cocoon-main-site/pom.xml Tue Apr 10 10:20:04 2012
@@ -17,9 +17,7 @@
specific language governing permissions and limitations
under the License.
-->
-<!--+
- | @version $Id$
- +-->
+<!-- $Id$ -->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
@@ -50,54 +48,53 @@
</distributionManagement>
<scm>
-<!-- repeated here so that maven-site is not appended -->
+ <!-- repeated here so that maven-site is not appended -->
<connection>scm:svn:http://svn.apache.org/repos/asf/cocoon/trunk</connection>
<developerConnection>scm:svn:https://svn.apache.org/repos/asf/cocoon/trunk</developerConnection>
<url>http://svn.apache.org/viewcvs/cocoon/trunk</url>
</scm>
- <reporting>
- <excludeDefaults>true</excludeDefaults>
+ <build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-project-info-reports-plugin</artifactId>
- <reportSets>
- <reportSet>
- <reports>
- <report>project-team</report>
- <report>mailing-list</report>
- <report>cim</report>
- <report>issue-tracking</report>
- <report>license</report>
- </reports>
- </reportSet>
- </reportSets>
+ <artifactId>maven-site-plugin</artifactId>
+ <version>3.0</version>
+ <configuration>
+ <locales>en</locales>
+ <reportPlugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-project-info-reports-plugin</artifactId>
+ <version>2.4</version>
+ <configuration>
+ <dependencyDetailsEnabled>false</dependencyDetailsEnabled>
+ <dependencyLocationsEnabled>false</dependencyLocationsEnabled>
+ </configuration>
+ <reportSets>
+ <reportSet>
+ <reports>
+ <report>summary</report>
+ <report>project-team</report>
+ <report>mailing-list</report>
+ <report>issue-tracking</report>
+ <report>license</report>
+ </reports>
+ </reportSet>
+ </reportSets>
+ </plugin>
+ </reportPlugins>
+ </configuration>
+ <executions>
+ <execution>
+ <id>attach-descriptor</id>
+ <goals>
+ <goal>attach-descriptor</goal>
+ </goals>
+ </execution>
+ </executions>
</plugin>
</plugins>
- </reporting>
-
- <profiles>
- <profile>
- <id>daisy</id>
- <build>
- <plugins>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-site-plugin</artifactId>
- </plugin>
- <plugin>
- <groupId>org.daisycms</groupId>
- <artifactId>daisy-maven-plugin</artifactId>
- <configuration>
- <navDocId>1203</navDocId>
- <collection>cdocs-site-main</collection>
- <skipFirstNavigationDocumentLevel>false</skipFirstNavigationDocumentLevel>
- </configuration>
- </plugin>
- </plugins>
- </build>
- </profile>
- </profiles>
+ </build>
</project>
Added: cocoon/trunk/site/cocoon-main-site/src/site/resources/images/external.png
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-main-site/src/site/resources/images/external.png?rev=1311664&view=auto
==============================================================================
Binary file - no diff available.
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/resources/images/external.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Copied: cocoon/trunk/site/cocoon-main-site/src/site/site.xml (from r1311155, cocoon/cocoon3/trunk/parent/src/site/site.xml)
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-main-site/src/site/site.xml?p2=cocoon/trunk/site/cocoon-main-site/src/site/site.xml&p1=cocoon/cocoon3/trunk/parent/src/site/site.xml&r1=1311155&r2=1311664&rev=1311664&view=diff
==============================================================================
--- cocoon/cocoon3/trunk/parent/src/site/site.xml (original)
+++ cocoon/trunk/site/cocoon-main-site/src/site/site.xml Tue Apr 10 10:20:04 2012
@@ -19,33 +19,66 @@
-->
<!-- $Id$ -->
<project xmlns="http://maven.apache.org/DECORATION/1.1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://maven.apache.org/DECORATION/1.1.0 http://maven.apache.org/xsd/decoration-1.1.0.xsd"
- name="Cocoon 3">
+ xsi:schemaLocation="http://maven.apache.org/DECORATION/1.1.0 http://maven.apache.org/xsd/decoration-1.1.0.xsd"
+ name="Cocoon">
<skin>
<groupId>org.apache.cocoon</groupId>
<artifactId>cocoon-thien-maven-site-skin</artifactId>
<version>1.0.1</version>
</skin>
-
+
<body>
- <menu name="Documentation">
- <item name="Index" href="index.html" />
- <item name="Changelog" href="changes-report.html" />
- <item name="Roadmap" href="roadmap.html" />
- <item name="Userguide" href="reference/index.html" />
- <item name="Features" href="features.html" />
+ <menu name="About Cocoon">
+ <item name="Welcome" href="./index.html"/>
+ <item name="Features" href="./1363_1_1.html"/>
+ <item name="Versions & Download" href="./1284_1_1.html"/>
+ <item name="Professional Services" href="./1271_1_1.html"/>
+ <item name="Who uses Cocoon?" href="./1365_1_1.html" collapse="true">
+ <item name="Products" href="./1365_1_1.html"/>
+ <item name="Live Sites - 2.2" href="./706_1_1.html"/>
+ <item name="Live Sites - 2.1.8" href="./705_1_1.html"/>
+ <item name="Live Sites - 2.1.7" href="./704_1_1.html"/>
+ <item name="Live Sites - 2.1.6" href="./703_1_1.html"/>
+ <item name="Live Sites - 2.1.4" href="./701_1_1.html"/>
+ <item name="Live Sites - 2.1.3" href="./700_1_1.html"/>
+ <item name="Live Sites - 2.1.2" href="./699_1_1.html"/>
+ <item name="Live Sites - 2.1.1" href="./698_1_1.html"/>
+ <item name="Live Sites - 2.1" href="./697_1_1.html"/>
+ <item name="Live Site Template" href="./696_1_1.html"/>
+ </item>
+ <item name="Weblogs" href="./1272_1_1.html"/>
+ <item name="History" href="./1178_1_1.html"/>
+ <item name="Privacy Policy" href="./1508_1_1.html"/>
+ </menu>
+
+ <menu name="Getting Started">
+ <item name="Tutorials" href="./1370_1_1.html"/>
</menu>
- <menu name="Project">
- <item name="License" href="license.html" />
- <item name="Team list" href="team-list.html" />
- <item name="Contributions" href="contributions.html" />
- <item name="Mailing lists" href="mail-lists.html" />
- <item name="Building" href="building.html" />
- <item name="Source Repository" href="source-repository.html" />
- <item name="API" href="apidocs/index.html" />
- <item name="Issue Tracking" href="https://issues.apache.org/jira/browse/COCOON3" />
- <item name="Download" href="download.html" />
+
+ <menu name="Getting Better">
+ <item name="About the online documentation" href="./1286_1_1.html"/>
+ <item name="Presentations" href="./1287_1_1.html"/>
+ <item name="How-Tos" href="./1368_1_1.html"/>
+ <item name="Articles" href="./1288_1_1.html"/>
+ <item name="Books" href="./1289_1_1.html"/>
+ </menu>
+
+ <menu name="Getting involved">
+ <item href="1273_1_1.html" name="How to contribute?"/>
+ <item href="1275_1_1.html" name="Communication tools that we use"/>
+ <item href="1276_1_1.html" name="Other tools that we use"/>
+ <item collapse="true" href="1199_1_1.html" name="Committer's and contributor's section">
+ <item href="1199_1_1.html" name="Releasing Cocoon"/>
+ <item href="798_1_1.html" name="Working with Cocoon from SVN">
+ <item href="798_1_1.html" name="Building Cocoon 2.2"/>
+ <item href="1214_1_1.html" name="How to mount the Cocoon 2.2 projects in Eclipse"/>
+ <item href="1164_1_1.html" name="How to solve Maven 2 problems"/>
+ </item>
+ <item href="1301_1_1.html" name="Debugging Cocoon in Eclipse"/>
+ </item>
</menu>
+
+ <menu ref="reports" inherit="bottom"/>
</body>
</project>
Added: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1164_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1164_1_1.xml?rev=1311664&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1164_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1164_1_1.xml Tue Apr 10 10:20:04 2012
@@ -0,0 +1,63 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+ 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.
+ --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Main Site - How to solve Maven 2 problems</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <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><section name="Cleanup your local repository" style="background:none;padding:0;"/><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\<Your Login Name>\.m2\repository
+[Unix] ~/.m2/repository
+</pre><p>or different locations can be configured in <tt>~/.m2/settings.xml.</tt></p><section name="Remove a configured Mirror" style="background:none;padding:0;"/><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><section name="Configure a mirror" style="background:none;padding:0;"/><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><settings>
+Â <mirrors>
+Â Â Â <mirror>
+Â Â Â Â Â <mirrorOf>central</mirrorOf>
+Â Â Â Â Â <id>ibiblioEuropeanMirror</id>
+Â Â Â Â Â <url>http://mirrors.dotsrc.org/maven2</url>
+Â Â Â </mirror>
+Â Â Â <!--
+Â Â Â <mirror>
+Â Â Â Â Â <mirrorOf>central</mirrorOf>
+Â Â Â Â Â <id>ibiblioAustralianMirror</id>
+Â Â Â Â Â <url>http://public.planetmirror.com/pub/maven2</url>
+Â Â Â </mirror>Â Â Â
+Â Â Â Â -->
+Â </mirrors>
+</settings></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>Common Maven errors</h1><section name="java.lang.OutOfMemoryError: Java heap space" style="background:none;padding:0;"/><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>And when your build works</h1><section name="Run Maven in offline mode" style="background:none;padding:0;"/><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><section name="Setup a company internal proxy repository" style="background:none;padding:0;"/><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>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1164_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1164_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1164_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1178_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1178_1_1.xml?rev=1311664&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1178_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1178_1_1.xml Tue Apr 10 10:20:04 2012
@@ -0,0 +1,72 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+ 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.
+ --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Main Site - History</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">History</h1><h1>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
+/docs and copy them to the right place.</p><p>The problem was that people were continously messing up the docs. Few people
+want to write documentation for open source projects; when they do, you thank
+them and don't complain about coherence of style and stuff like that. Or you
+won't have any docs at all.</p><p>The solution was obvious: we needed a way to separate style from content. In
+late 1998 the first XSL working draft was released and IBM made a Java XSL
+processor, LotusXSL, available. I downloaded both and started to play around
+with what was later called XSLT. While playing with this stuff, I quickly grew
+tired of typing a command line, moving to the browser to see the result, over
+and over. I wanted a less tedious change-transform-reload cycle.</p><p>So I wrote a servlet that handled the tedious bits for me; I could modify the
+stylesheet, hit reload on the browser, and the servlet would handle everything.
+This was at the very end of 1998 and Ron Howard's movie Cocoon was playing on
+the television, which explains the weird name only partially. I believed at the
+time that these technologies were a key part of the future of the Web, so a
+cocoon was just what was needed to allow them to incubate and grow stronger.</p><p>Apache Cocoon 1.0 was a servlet, about 100 lines of code, that used XML4J
+(later Apache Xerces) and LotusXSL (later Apache Xalan) to transform an XML file
+with an XSL stylesheet. At that time, XSLT, XPath and XSL:FO were still part of
+one big spec. I didn't think it was very useful for anyone else so I kept it on
+my disk for a few months. Then, around March 1999, on the jserv-dev mail list
+somebody was asking about XSL, and I said that I'd written a servlet that did
+all that transformation on the server side. Many people asked for it, so I
+requested a formal vote and the Apache Cocoon project was started under the
+java.apache.org umbrella.</p><p>The 1.0 version contained very little code, but lots of examples and some
+simple docs that explained what XSL was and why I thought it was important to
+learn it. After its release, people started joining active development, and we
+turned a small servlet into a full XML-based publishing system, which is now
+used in many production sites around the world.</p><p>But Cocoon 1.x was designed when the XML world was very young and experience
+was very small and it was based under several design choices that turned to be
+very limiting. So, around November 1999, I expressed the intention to work on
+the next generation (what people started calling Cocoon2 or simply C2) to solve
+all those architectural issues.</p><p>It took two years and three different project leaders to finish Cocoon 2.0
+but we made it. It's an XML framework that raises the usage of XML and XSLT
+technologies for server applications to a new level. Designed for performance
+and scalability around pipelined SAX processing, Cocoon offers a flexible
+environment based on the separation of concerns between content, logic and
+style. A centralized configuration system and sophisticated caching enable you
+to create, deploy, and maintain rock-solid XML server applications.</p><p>Cocoon was designed as an abstract engine that could be connected to almost
+anything, but it ships with servlet and command line connectors. The servlet
+connector allows you to call Cocoon from your favorite servlet engine or
+application server. You can install it beside your existing servlets or JSPs.
+The command line interface allows you to generate static content as a batch
+process. It can be useful to pre-generate those parts of your site that are
+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>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>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
+their own build cycle. This in turn should allow for binary releases again.</p></div></div>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1178_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1178_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1178_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1199_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1199_1_1.xml?rev=1311664&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1199_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1199_1_1.xml Tue Apr 10 10:20:04 2012
@@ -0,0 +1,183 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+ 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.
+ --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Main Site - Releasing Cocoon</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <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>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><section name="Java" style="background:none;padding:0;"/><p>Make sure that you use Java 1.4. Usually this means setting JAVA_HOME
+correctly.</p><section name="GnuPG" style="background:none;padding:0;"/><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><section name="Maven 2" style="background:none;padding:0;"/><h3>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>
+<li>in the case that your local username is different from your username at
+people.apache.org, configure it at ~/.m2/settings.xml.</li>
+<li>point to an empty local repository</li>
+</ul><pre><settings>
+ <localRepository>[path to an existing, empty directory</localRepository>
+Â <servers>
+Â Â Â <server>
+Â Â Â Â Â <id>cocoon-staging-repo</id>
+Â Â Â Â Â <username>[your username on people.apache.org]</username>
+Â Â Â Â Â <filePermissions>664</filePermissions>
+Â Â Â Â Â <directoryPermissions>775</directoryPermissions>
+Â Â Â </server>
+Â </servers>
+</settings></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>Win32 based systems</h3><div class="fixme"><div><strong>Fixme: </strong>TBD</div></div><section name="Daisy" style="background:none;padding:0;"/>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/>
+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>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="-N"<br/>
+</tt></li>
+<li><tt>mvn -N -Dusername=</tt><tt>[svn-user-name]</tt><tt> -Dpassword=********
+release:perform -Darguments="-N
+</tt><tt>-Dgpg.passphrase='[secret_passphrase_here]'</tt><tt>" </tt><tt>-P
+release</tt></li>
+</ol>Take care to manually change all poms that have the released pom as a parent.
+For example you release cocoon-blocks-modules under version 3, before it was
+2-SNAPSHOT. The next version increment of that pom is thus 3-SNAPSHOT, and you
+should manually change all poms that have 2-SNAPSHOT for this parent to
+3-SNAPSHOT. Otherwise the trunk build will use "old" 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>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
+managed by the root POM of Cocoon. By replacing all SNAPSHOT dependencies in the
+step before, you also have replaced the SNAPSHOT version of the parent with a
+released version. Make sure that the module that you want to release also works
+with the versions set in the <em>released root POM</em>! Otherwise you have to
+override them by setting them manually in the module's POM (sic).</li>
+<li><tt>mvn -Dusername=[svn-user-name] -Dpassword=******** release:prepare</tt>
+</li>
+<li><tt>mvn -Dusername=[svn-user-name] -Dpassword=******** release:perform
+-Darguments="-Dgpg.passphrase='[secret_passphrase_here]' -P
+release,daisy,localDocs,javadocs-script" -P
+release,daisy,localDocs,javadocs-script</tt></li>
+<ul>
+<li><tt><tt>release </tt>... </tt>adds all plugins to the build lifecycle which
+are only necessary at release time (e.g. the GPG plugin)</li>
+<li><tt>daisy ... </tt>adds the Daisy export plugin to the lifecycle of the site
+module</li>
+<li><tt>j<tt>avad</tt></tt><tt>ocs-script ... </tt>adds a special report to the
+report generation phase which adds an <tt>apidocs </tt>directory to the site
+output. This directory then contains a script which pulls the Javadocs from a
+Maven repository and unpacks it.</li>
+<li><tt>localDocs ... </tt>configures the target directory of the deploy
+process. This profile has to be configured in the <em>local
+</em><tt>settings.xml</tt>!</li>
+</ul>
+
+<li>if <tt>SNAPSHOT </tt>dependencies have been replaced before, point again to
+them</li>
+<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><section name="Additional instructions for special modules" style="background:none;padding:0;"/><h3>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.
+You have to use <em>the to-be-released</em> version.</li>
+<li>Before you can invoke the release procedure from above, run <tt>mvn clean
+install</tt> before. This has to be done because of a bug when Maven tries to
+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>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
+within its pom.xml file but are being resolved at runtime. This means that
+before you run invoke the release procedure, go to the file
+<a href="http://svn.apache.org/repos/asf/cocoon/trunk/tools/cocoon-maven-plugin/src/main/java/org/apache/cocoon/maven/rcl/PrepareWebappMojo.java">PrepareWebappMojo.java</a>
+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>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>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>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>Step 7: Publish the artifacts</h1>If the vote passes, the artifacts are copied to public locations:<section name="Maven repository" style="background:none;padding:0;"/>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>.<section name="Apache distribution site" style="background:none;padding:0;"/>Then copy the distribution artifacts (aka Non-Maven release artifacts):<h1>Step 8: Announce the release</h1><div class="fixme"><div><strong>Fixme: </strong>Add a template here</div></div><h1>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
+enough).<br/>
+As for 3th of Janury, 2008 there are two Cocoon committers with necessary karma:
+<ul>
+<li>Grzegorz Kossakowski (gkossakowski (at) apache.org)</li>
+<li>Carsten Ziegeler (cziegeler (at) apache.org)</li>
+</ul>I (Grzegorz) volunteered to take care of administration of these fields
+whenever need occur. When a new version is being released, write me a short
+e-mail using following template:<pre>Hi Grzegorz!
+
+I would like you to ask for adjusting values of custom Cocoon project fields in JIRA. Here comes the info about released artifacts:
+
+Aritfact name: cocoon-forms-impl
+Version in the POM file *before* preparing the release: 1.0.0-RC2-SNAPSHOT
+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>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>
+<li>You can shortcut the execution by specifying both goals in one:<br/>
+<tt>mvn -N release:prepare release:perform ...</tt></li>
+<li>Verify a GPG signature: <tt>gpg --verify gnupg-x.x.x.tar.gz.sig
+gnupg-x.x.x.tar.gz</tt></li>
+<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>More readings</h1><ul>
+<li>
+<a href="http://maven.apache.org/plugins/maven-release-plugin/">Documentation of
+the Maven release plugin</a></li>
+<li><a href="http://maven.apache.org/guides/mini/guide-releasing.html">Guide to
+use the Maven 2 release plugin</a></li>
+<li>GnuPG</li>
+<ul>
+<li><a href="http://www.queen.clara.net/pgp/art4.html">GnuPG tutorial</a></li>
+<li>
+<a href="http://alfie.ist.org/projects/gpg-party/gpg-party.de.html">Information
+about a key signing party containing useful information how GnuPG is used</a>
+(german)</li>
+</ul>
+
+</ul></div></div>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1199_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1199_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1199_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1214_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1214_1_1.xml?rev=1311664&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1214_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1214_1_1.xml Tue Apr 10 10:20:04 2012
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+ 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.
+ --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Main Site - How to mount the Cocoon 2.2 projects in Eclipse</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">How to mount the Cocoon 2.2 projects in Eclipse</h1><p>After following the <a href="798_1_1.html">Working with Cocoon 2.2 from
+trunk</a> page you can mount the projects in Eclipse.</p><p>From the directory where you installed Cocoon trunk, we refer to it as
+/trunk, run</p><pre>mvn eclipse:clean
+</pre><p>first to remove any left over eclipse files. Then run</p><pre>mvn -P allblocks eclipse:eclipse</pre><p>This creates <tt>classpath</tt> and <tt>.project</tt> files for each module.
+</p><p>Next start Eclipse and make sure you haven't got trunk mounted as a project
+already. Also remove <tt>.classpath</tt> and <tt>.project</tt> files possibly
+remaining in <tt>/trunk</tt> from a previous project mount. Do
+<em>File-Import->Existing</em> projects into workspace, then point to your
+<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>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>.
+</p></div></div>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1214_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1214_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1214_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1223_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1223_1_1.xml?rev=1311664&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1223_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1223_1_1.xml Tue Apr 10 10:20:04 2012
@@ -0,0 +1,153 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+ 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.
+ --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Main Site - How to create documentation for a deployment unit (e.g. a block)?</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <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>Create the collection</h1><p>In Daisy, open Administration -> Manage collections.<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/>
+Note the id of the collection (in this case <em>7</em>).</p><h1>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><user friendly name> 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 "link to
+new document" 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>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/>
+</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>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/>
+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>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.<section name="Configure the root pom.xml" style="background:none;padding:0;"/>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><properties>
+ [...]
+ <docs.m.forms.version>1.0</docs.m.forms.version>
+ <docs.m.forms.relPath>blocks/forms/${docs.m.forms.version}/</docs.m.forms.relPath>Â Â Â Â
+</properties>
+</pre>Open the pom.xml in the root and find the plugin with artifactId
+daisy-maven-plugin. Under <tt>collections</tt> add<pre> <collection>
+ <name>cdocs-forms</name>
+ <path>${docs.m.forms.relPath}</path>
+ </collection></pre>Try to keep the collections in alphabetical order as well.<section name="Configure the block pom.xml" style="background:none;padding:0;"/><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 <build>, <plugins>, 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>Â Â Â <build>
+Â Â Â Â Â Â Â <plugins>
+Â Â Â Â Â Â Â Â Â Â Â <plugin>
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <groupId>org.daisycms</groupId>
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <artifactId>daisy-maven-plugin</artifactId>
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <configuration>
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <navDocId>1152</navDocId>
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <collection>cdocs-forms</collection>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
+ <skipFirstNavigationDocumentLevel>true</skipFirstNavigationDocumentLevel>
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â </configuration>
+Â Â Â Â Â Â Â Â Â Â Â </plugin>
+Â Â Â Â Â Â Â </plugins>
+Â Â Â </build></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> <distributionManagement>
+ <site>
+ <id>website</id>
+ <url>${docs.deploymentBaseUrl}/${docs.m.forms.relPath}</url>
+ </site>
+ </distributionManagement>
+ <properties>
+ <docs.name><strong>Cocoon Forms</strong></docs.name>
+ <docs.version>${docs.m.forms.version}</docs.version>
+ </properties>
+</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><section name="Configure the site pom.xml" style="background:none;padding:0;"/>Open the pom.xml in the site and add a module to the section Cocoon Blocks:
+<pre> <module>../blocks/cocoon-forms/cocoon-forms-impl</module>
+</pre>Keep the modules in alphabetical order to ease maintenance.</div></div>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1223_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1223_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1223_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1256_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1256_1_1.xml?rev=1311664&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1256_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1256_1_1.xml Tue Apr 10 10:20:04 2012
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+ 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.
+ --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Main Site - How to build the site locally</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">How to build the site locally</h1><p>This page explains how to build the Cocoon 2.2 documentation site with Maven2
+and the daisy-maven-plugin.</p><p>This plugin assumes that each block has its own collection and navigation
+document.</p><h1>Configure settings.xml</h1><p>The documents can only be exported by a user with admin rights to the Daisy
+repository. We have created such a user <tt>daisy-export</tt>. The password for
+this user is available in a <tt>daisy-export-user-<tt>password.txt</tt>
+</tt>file in the home directory of the daisy user. If you want to use your own
+Daisy user, make sure that you have administration rights.</p><p>Open the <tt>~/.m2/setting.xml</tt> and add the following:</p><pre><settings>
+
+ [...]
+
+ <profiles>
+Â <profile>
+ <id>localDocs</id>
+ <properties>
+ <docs.deploymentBaseUrl>file:///cocoon-site</docs.deploymentBaseUrl>
+ </properties>
+ </profile>
+ </profiles>
+
+ <servers>
+ <server>
+ <id>cocoon-daisy</id>
+ <username>daisy-export</username>
+ <password><strong>SECRET PASSWORD HERE</strong></password>
+ </server>
+ </servers>
+
+</settings>
+</pre><h1>Build all modules required for the site generation</h1><pre>cd trunk
+mvn install -P daisy</pre><h1>Build the site</h1><pre>cd trunk/site
+mvn site -o -P daisy,docs-sites
+</pre><div class="note"><div><strong>Note: </strong>You don't have to build the complete site for every module every
+time. You can also go to a module, that is configured to provide docs, of your
+choice and build its docs only if this fits your needs.</div></div><h1>Deploy the site locally</h1><p>Deploy the site using the "localDocs" profile.</p><pre>mvn site:deploy -o -P daisy,docs-sites,localDocs
+</pre><p>If you want to checkin the local docs build to SVN in order to publish them,
+make sure that the profile above (localDocs) points to a local directory which
+is a checkout of our docs from SVN
+(<a href="http://svn.apache.org/repos/asf/cocoon/site/site/">http://svn.apache.org/repos/asf/cocoon/site/site/</a>).
+<br/>
+There is a guide with additional information about <a href="1418_1_1.html">how to
+publish our docs</a>.</p></div></div>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1256_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1256_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1256_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1271_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1271_1_1.xml?rev=1311664&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1271_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1271_1_1.xml Tue Apr 10 10:20:04 2012
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+ 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.
+ --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Main Site - Professional Services</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Professional Services</h1><p>These companies provide professional services around Apache Cocoon (sorted by
+alphabetical order):</p><ul>
+<li><strong><a href="http://www.agilepartners.com">Agile Partners</a></strong>,
+New York City and Chicago, USA<br/>
+Development and consulting</li>
+<li><strong><a href="http://www.hippo.nl/en/home">Hippo</a></strong>, Amsterdam,
+Netherlands <br/>
+Development, consulting and training</li>
+<li>
+<strong><a href="http://www.indoqa.com/en/services/opensource-technology">{Indoqa}</a>,</strong>
+Vienna, Austria<br/>
+Consulting and training (Europe)</li>
+<li><strong><a href="http://www.fiveone.org">Jeremy Quinn</a></strong> London,
+UK<br/>
+Consultancy</li>
+<li><strong><a href="http://www.otego.com">Otego AG</a></strong>, Zürich,
+Switzerland<br/>
+Consulting and training in Switzerland</li>
+<li><strong><a href="http://outerthought.org/">Outerthought</a></strong>,
+Belgium<br/>
+International Cocoon and <a href="http://www.daisycms.org/">Daisy CMS</a>
+projects and services</li>
+<li><strong><a href="http://www.sourcesense.com/">Sourcesense</a></strong>
+Italy, Netherlands, UK<br/>
+European consulting and training</li>
+</ul>If you do not find your site here, use the <em>Edit</em> link below and add
+yourself. If you are not familiar with the CMS, read the <em>General
+documentation</em> section of <a href="1273_1_1.html">How to contribute?</a>.</div></div>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1271_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1271_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1271_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1272_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1272_1_1.xml?rev=1311664&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1272_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1272_1_1.xml Tue Apr 10 10:20:04 2012
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+ 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.
+ --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Main Site - Weblogs</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Weblogs</h1><p>A list of feeds that have Apache Cocoon as one of their topics:</p><ul>
+<li><a href="http://www.andrewsavory.com/blog/">Andrew Savory</a></li>
+<li><a href="http://blogs.hippo.nl/reijn/">Jeroen Reijn</a></li>
+<li><a href="http://www.indoqa.com/en/people/reinhard.poetz/">Reinhard Pötz</a>
+</li>
+<li><a href="http://blog.reverycodes.com/">Vadim Gritsenko</a></li>
+</ul>If you do not find your feed here, use the <em>Edit</em> link below and add
+yourself. If you are not familiar with the CMS, read the <em>General
+documentation</em> section of <a href="1273_1_1.html">How to contribute?</a>.</div></div>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1272_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1272_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1272_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1273_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1273_1_1.xml?rev=1311664&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1273_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1273_1_1.xml Tue Apr 10 10:20:04 2012
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+ 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.
+ --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Main Site - How to contribute?</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">How to contribute?</h1><h1>Code</h1><p>TBD</p><h1>General documentation</h1><p>These instructions only work if you have an active account in our Daisy CMS
+and got the doc editor role assigned. If you haven't, create your account at
+<a href="http://cocoon.zones.apache.org/daisy/registration">http://cocoon.zones.apache.org/daisy/registration</a>
+and ask at dev[_at_]cocoon.apache.org for editing rights.</p><div class="note"><div><strong>Note: </strong>Doc editors are not allowed to publish a document. This can only
+be done by Apache Cocoon committers.</div></div><section name="Editing a document" style="background:none;padding:0;"/><p>Simply follow the "Edit" link at the bottom of a page, login in and select
+<em>Page Actions - Edit</em> from the menu.</p><section name="Adding a document" style="background:none;padding:0;"/><p>Go to http://cocoon.zones.apache.org/daisy/, login and select the
+documentation site where you want to add your new document. Select <em>New
+Document</em> from the menu. The recommended document type is <em>Cocoon
+document</em>.<br/>
+If you want to make your new document appear in a navigation menu, click on
+<em>Go to navigation</em> document below the navigation menu and select
+<em>Page Actions - Edit</em>.</p><section name="What happens once I've added or edited a document?" style="background:none;padding:0;"/><p>The moment you submit a new or changed document an email is sent to docs at
+cocoon dot apache dot org. An entry is also added to the list on the Daisy
+<a href="NO_LINK">Cocoon Site Overview</a> page. A Cocoon committer should
+then see the change, review it and make it live.</p><h1>Sitemap component documentation</h1><p>For documenting sitemap components, we use a system whereby certain parts of
+the documentation are extracted automatically from the Java sources using a tool
+called sitemaptags2daisy.</p><p>If you are not a committer, make sure that you have checked out the latest
+version of the Java source file from SVN, make your changes and create a patch
+file. Create a new patch issue in JIRA and add your diff file.</p><section name="Editing the documentation of a sitemap component" style="background:none;padding:0;"/><p>Only edit the content of the the Long Description part in Daisy. The short
+description and the value of the fields are automatically assigned from the Java
+sources, so if you change them in Daisy, these changes will get overwritten the
+next time the sitemaptags2daisy tool is run.</p><section name="Adding documentation for a new sitemap component" style="background:none;padding:0;"/><p>If running the sitemaptags2daisy tool is not an option (no time, no
+privileges, ...) then create manually a document of type "Sitemap Component". In
+the JavaClass field, enter the fully qualified name of the implementation class.
+Leave the other fields and the Short Description part empty, they will be
+assigned the next time the sitemaptags2daisy tool runs. Enter the documentation
+in the Long Description part.</p><section name="Adding javadoc tags" style="background:none;padding:0;"/><p>The following special javadoc tags are supported (none of these are strictly
+required by the sitemaptags2daisy tool):</p><ul>
+<li>@cocoon.sitemap.component.name<br/>
+default name with which this component is declared in the sitemap</li>
+<li>@cocoon.sitemap.component.documentation.disabled<br/>
+excludes the component from the documentation</li>
+<li>@cocoon.sitemap.component.documentation<br/>
+A short (one-paragraph) description of the component. Can contain HTML markup
+(preferably only inline tags).</li>
+<li>@cocoon.sitemap.component.documentation.caching<br/>
+A comment about the caching of this component. The cacheability of the component
+is figured out automatially by its implemented interfaces, but this tag allows
+to provide a short comment on the chaching conditions. This is mapped to a field
+in Daisy, thus should not contain HTML markup.</li>
+</ul>Next to these, the @deprecated tag is also synced with the Daisy document.
+<section name="Running the sitemaptags2daisy tool" style="background:none;padding:0;"/>TODO, see the README.txt in the sources for now.</div></div>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1273_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1273_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1273_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
Added: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1275_1_1.xml
URL: http://svn.apache.org/viewvc/cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1275_1_1.xml?rev=1311664&view=auto
==============================================================================
--- cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1275_1_1.xml (added)
+++ cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1275_1_1.xml Tue Apr 10 10:20:04 2012
@@ -0,0 +1,137 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+ 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.
+ --><document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/XDOC/2.0" xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd"><properties><title>Cocoon Main Site - Communication tools that we use</title><author email="[email protected]">Apache Cocoon Documentation Team</author></properties><body>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Communication tools that we use</h1><h1>Mailing lists</h1><p>See below for descriptions of the Cocon mailing lists. A list of all
+available lists as well as links is available a the
+<a href="mail-lists.html">overview</a> page.</p><p>When posting, please observe common-sense netiquette when posting. In
+particular:</p><ul>
+<li>When replying, please
+<a href="http://en.wikipedia.org/wiki/Top-posting#Inline_replying">edit the
+original message</a> and include only enough to establish context, not the
+entire message.</li>
+<li>Don't crosspost to the user and developer lists. The developers also read
+the users list.</li>
+<li>Only reply to a message if you are really posting a reply on that thread;
+don't use your mailer's "Reply" function as a shortcut to get the list address
+into the "To:" field. Instead, use your mailer's "new message" function to
+start a fresh thread. When people abuse "Reply" and just change the "Subject:"
+line to a new topic, it makes it harder for threaded mailreaders to display the
+subjects accurately. This can make it less likely that your message will be
+seen and replied to.</li>
+</ul>Regarding content:<ul>
+<li>Please ask your questions on the list. If someone helps you out, don't
+email them off-list to ask your next question. You will get the best answers if
+you stay on-list, and that way the question and answers can also benefit the
+current and future community.</li>
+<li>When asking for help, don't forget to include:</li>
+<ul>
+<li>The version of Cocoon you are using (the most important thing to not forget!
+:-)</li>
+<li>The servlet container (e.g. Jetty, Tomcat etc.) you are using.</li>
+<li>Platform details: JDK version and host OS</li>
+<li>Any relevant sitemap configuration, XSLT, Java or Javascript source code you
+are working with</li>
+<li>If you're getting an exception thrown, include the stack trace</li>
+</ul>
+
+<li>Don't just say that something "doesn't work"; explain (a) exactly what you
+did; (b) what you expected to happen; and (c) what happened instead of what you
+expected. That type of explanation gives people a lot more information to work
+with.</li>
+<li>If you can show that you at least made some effort to figure something out,
+you will in turn get a more helpful response. In particular, if you have in
+mind some idea that might help and it is an easy thing to try, don't post to the
+list to ask "Can I....". Just try it for yourself and see! :-)</li>
+<li>A very common response to user questions is "What are you trying to
+accomplish"? Try to supply that information when you first ask the question,
+and you will get a definitive answer that much sooner. Cocoon is a rich
+framework that gives you a lot of tools, so that it's not always obvious to new
+users which tool set is the best to use for a particular problem. New users
+sometimes get wrapped around the axle on some detail of the solution they are
+trying to make for a given scenario, and then end up posting to the list to ask
+how to do some exotic or bizarre thing. If you can take a step back and
+describe the scenario itself, the more experienced users may be able to suggest
+one or more simpler solutions.</li>
+<li>If you ask for help with something, and then you later figure it out for
+yourself, please follow up on the list and describe what you did to fix the
+problem. We like to prepend "SOLVED: " to the Subject: line when doing this.
+</li>
+<li>If you feel you must say "Please reply to me off-list, since I'm not
+subscribed", you can certainly do that; you just may or may not get a helpful
+reply! You'll almost certainly get better results if you let people repond
+on-list. See the Gmane links below to learn how easy it is to read the Cocoon
+lists without subscribing your own email address.</li>
+</ul><section name="User list" style="background:none;padding:0;"/>This is the general community help list and for Cocoon. Use it to learn
+Cocoon stuff, and share your own knowledge with somebody else! Don't forget to
+check the FAQ first. Also, this list is not really the place to ask questions
+about XSLT, HTML, CSS, Java programming, etc. Please consult the
+<a href="NO_LINK">Related Resources</a> page to find the right forum for
+asking those kinds of questions.Of course, new Cocoon releases are announced on this list.<h3>Gmane</h3>The Cocoon lists are mirrored on the <a href="http://gmane.org">Gmane</a>
+mail-to-news/web gateway.Â
+<a href="http://dir.gmane.org/gmane.text.xml.cocoon.user">This page</a>
+contains links you can use to subscribe your Usenet newsreader to the user list
+as a newsgroup, browse the list using Gmane's web interface, or subscribe your
+feedreader to a number of RSS feeds driven by the list.The lists are also <a href="http://www.nabble.com/Cocoon-f111.html">mirrored
+at Nabble</a>; you can browse or post. (Note the "child forums" links).<h3>Archive</h3>Archive sites can be found on the <a href="mail-lists.html">overview</a>
+page. Note that the mail-archive site changed in July 2003.<ul>
+<li>
+<a href="http://www.mail-archive.com/[email protected]/">http://www.mail-archive.com/[email protected]/
+</a>(since July 2003)</li>
+<li>
+<a href="http://www.mail-archive.com/cocoon-users%40xml.apache.org/">http://www.mail-archive.com/cocoon-users%40xml.apache.orgtwo</a>
+(before July 2003)</li>
+</ul><section name="Developer list" style="background:none;padding:0;"/>This list is for anyone interested in <a href="1273_1_1.html">working on Cocoon
+itself</a> (application developers making applications <em>with </em>Cocoon are
+Cocoon <em>users</em>). Anyone can read or post to this list; you don't have to
+be a Cocoon committer. Read this list if you want to learn more about the inner
+workings of Cocoon, or for detailed discussions about bugs or future enhancement
+requests. Please don't post routine user questions to the dev list, though.Â
+The topic of this list is <em>Cocoon development.</em>If you post a question in the user list, and the discussion gets so geeky
+that it has to move to the dev list... don't forget to come back to the user
+list with a "SOLVED:" post, once you've gotten everything ironed out! :-)The dev list gets automatic update notifications from the
+<a href="https://issues.apache.org/jira/browse/COCOON">JIRA issue tracking
+system</a> and from the
+<a href="http://cocoon.zones.apache.org/continuum/servlet/continuum/">Continuum
+build system</a>.<h3>Gmane</h3>The developer list is also
+<a href="http://dir.gmane.org/gmane.text.xml.cocoon.devel">available on
+Gmane</a>.<h3>Archive</h3>Archive sites can be found on the <a href="mail-lists.html">overview</a>
+page. Note that the mail-archive site changed in July 2003.<ul>
+<li>
+<a href="http://www.mail-archive.com/[email protected]/">http://www.mail-archive.com/[email protected]/
+</a>(since July 2003)</li>
+<li>
+<a href="http://www.mail-archive.com/cocoon-users%40xml.apache.org/">http://www.mail-archive.com/cocoon-users%40xml.apache.org/</a>
+(before July 2003)</li>
+</ul><section name="Documentation list" style="background:none;padding:0;"/>This <strong>read-only</strong> list is of interest to people who are
+<a href="1273_1_1.html">working on the Cocoon documentation</a>. It consists
+solely of update notifications from the <a href="TODO">Daisy docs CMS</a> and
+the <a href="http://wiki.apache.org/cocoon">Wiki</a>.<h3>Gmane</h3>On Gmane,
+<a href="http://dir.gmane.org/gmane.text.xml.cocoon.documentation">right
+here</a>.<section name="SVN repository update list" style="background:none;padding:0;"/>This list is probably only of interest to hard-core Cocoon developers. It is
+a <strong>read-only</strong> list that consists solely of automated update
+notifications from the Subversion source code management system. The name
+"cocoon-cvs" is a holdover from when the Cocoon project used CVS.<h3>Gmane</h3>This one is <a href="http://dir.gmane.org/gmane.text.xml.cocoon.cvs">on Gmane
+too</a>.<h1>Wiki</h1>There's a <a href="http://wiki.apache.org/cocoon/">Cocoon Wiki</a>. YMMV
+<h1>IRC</h1>The Cocoon community chat room is the #cocoon channel at
+<a href="http://freenode.net">freenode.net</a>. Get over there and shake things
+up!<h1>JIRA</h1>Bug/issue tracking on the Cocoon project
+<a href="https://issues.apache.org/jira/browse/COCOON">uses Atlassian
+JIRA</a>. This is a communication medium in its own right. Updates to JIRA
+issues trigger notifications to the dev mailing list, so you can monitor each
+issue's mini-discussion from the dev mailing list.</div></div>
+ </body></document>
\ No newline at end of file
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1275_1_1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1275_1_1.xml
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: cocoon/trunk/site/cocoon-main-site/src/site/xdoc/1275_1_1.xml
------------------------------------------------------------------------------
svn:mime-type = text/xml
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.