You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by cz...@apache.org on 2003/10/12 15:31:55 UTC
cvs commit: cocoon-2.1/src/documentation/xdocs/plan changes-doc.xml
cziegeler 2003/10/12 06:31:55
Modified: src/documentation/xdocs/tutorial tutorial-rmi-generator.xml
tutorial-develop-webapp.xml tutorial-generator.xml
src/documentation/xdocs/howto book.xml
howto-xindice-xmlform.xml
src/documentation/xdocs/faq faq-generators.xml
faq-matchers.xml faq-transformers.xml
faq-configure-environment.xml faq-serializers.xml
faq-sitemap.xml faq-selectors.xml
src/documentation/xdocs/plan changes-doc.xml
Added: src/documentation/xdocs/developing deliquick.xml
extending.xml parent-component-manager.xml
datasources.xml book.xml httprequest.xml deli.xml
source.xml web3.xml index.xml avalon.xml
src/documentation/xdocs/installing book.xml updating.xml
requirements.xml tests.xml jars.xml index.xml
Removed: src/documentation/xdocs/userdocs/developer web3.xml
deliquick.xml preface.xml book.xml httprequest.xml
deli.xml extending.xml datasources.xml
src/documentation/xdocs/userdocs/installation jars.xml
tests.xml index.xml updating.xml requirements.xml
book.xml
src/documentation/xdocs/userdocs/developer/avalon
parent-component-manager.xml avalon.xml source.xml
book.xml preface.xml
Log:
Continue rearranging docs to the old places :(
This will take some time - so please be patient...
Revision Changes Path
1.4 +1 -1 cocoon-2.1/src/documentation/xdocs/tutorial/tutorial-rmi-generator.xml
Index: tutorial-rmi-generator.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/tutorial/tutorial-rmi-generator.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- tutorial-rmi-generator.xml 2 Sep 2003 13:17:33 -0000 1.3
+++ tutorial-rmi-generator.xml 12 Oct 2003 13:31:53 -0000 1.4
@@ -366,7 +366,7 @@
</s3>
<s3 title="Interface(s)">
- <p>Following the somewhat little pointers on develop-part of the Cocoon-website <link href="../userdocs/developer/extending.html">Extending Apache Cocoon van The Apache XML Project</link>), we find that the only interface that should be implemented is the Generator interface in the <strong>org.apache.cocoon.generation</strong> package, so we will try to give an overview as complete as possible for now.
+ <p>Following the somewhat little pointers on develop-part of the Cocoon-website <link href="../developing/extending.html">Extending Apache Cocoon van The Apache XML Project</link>), we find that the only interface that should be implemented is the Generator interface in the <strong>org.apache.cocoon.generation</strong> package, so we will try to give an overview as complete as possible for now.
</p>
<s4 title="Generator">
1.4 +1 -1 cocoon-2.1/src/documentation/xdocs/tutorial/tutorial-develop-webapp.xml
Index: tutorial-develop-webapp.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/tutorial/tutorial-develop-webapp.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- tutorial-develop-webapp.xml 2 Sep 2003 13:17:33 -0000 1.3
+++ tutorial-develop-webapp.xml 12 Oct 2003 13:31:53 -0000 1.4
@@ -29,7 +29,7 @@
The areas addressed are Logic, Content, Style, and Management. There
are different mechanisms for each.</p>
<p>In order to learn how to use Cocoon, first make sure that you
- <link href="../userdocs/installation/index.html">install</link> it properly, then investigate
+ <link href="../installing/index.html">install</link> it properly, then investigate
the many <link href="../overview.html#samples">samples</link>.
The following screenshots come from the
"<code>tutorial</code>" that is provided with Cocoon.
1.8 +4 -4 cocoon-2.1/src/documentation/xdocs/tutorial/tutorial-generator.xml
Index: tutorial-generator.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/tutorial/tutorial-generator.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- tutorial-generator.xml 2 Sep 2003 13:53:11 -0000 1.7
+++ tutorial-generator.xml 12 Oct 2003 13:31:53 -0000 1.8
@@ -34,7 +34,7 @@
functionality of Cocoon will be an important feature for Cocoon's
viability as a broadly used application framework. Though the
documentation on
- <link href="../userdocs/developer/extending.html">"Extending Cocoon"</link>
+ <link href="../developing/extending.html">"Extending Cocoon"</link>
(at least at this writing) seems to have a hard time imagining
applications for custom generators outside of the bizarre, I
imagine several scenarios which could call for it:</p>
@@ -49,7 +49,7 @@
optimization in custom generators that just do not seem
reasonable to expect out of the auto-generated code that XSPs
produce. The current
- <link href="../userdocs/config/performancetips.html">Performance Tips</link>
+ <link href="../performancetips.html">Performance Tips</link>
documentation seems to lead in this direction.</li>
<li>Customized control over the caching behaviour if not
@@ -93,10 +93,10 @@
<li>Read
<link href="../userdocs/concepts/index.html">Cocoon Concepts</link>
, as well as
- <link href="../userdocs/developer/extending.html">Extending Cocoon</link>
+ <link href="../developing/extending.html">Extending Cocoon</link>
, and the broad overview of
- <link href="../userdocs/developer/avalon/preface.html">Avalon</link>
+ <link href="../developing/avalon.html">Avalon</link>
, the framework upon which Cocoon is built.</li>
1.4 +1 -1 cocoon-2.1/src/documentation/xdocs/howto/book.xml
Index: book.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/howto/book.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- book.xml 4 Sep 2003 14:08:32 -0000 1.3
+++ book.xml 12 Oct 2003 13:31:54 -0000 1.4
@@ -12,7 +12,7 @@
<menu-item label="XMLForm" href="xmlform-wizard/howto-xmlform-wizard.html"/>
<menu-item label="Paginator" href="howto-paginator-transformer.html"/>
<menu-item label="HTML-PDF" href="howto-html-pdf-publishing.html"/>
- <menu-item label="Web Syndication" href="../userdocs/components/generators/wsproxy-generator.html"/>
+ <menu-item label="Web Syndication" href="../userdocs/generators/wsproxy-generator.html"/>
<menu-item label="i18n XMLForm" href="howto-i18n-xmlform.html"/>
<menu-item label="Flow Debugger" href="howto-flow-debugger.html"/>
<menu-item label="Xindice XMLForm" href="howto-xindice-xmlform.html"/>
1.5 +1 -1 cocoon-2.1/src/documentation/xdocs/howto/howto-xindice-xmlform.xml
Index: howto-xindice-xmlform.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/howto/howto-xindice-xmlform.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- howto-xindice-xmlform.xml 2 Sep 2003 13:17:34 -0000 1.4
+++ howto-xindice-xmlform.xml 12 Oct 2003 13:31:54 -0000 1.5
@@ -737,7 +737,7 @@
using information stored in the DB. Remember that everything you
have just built is reusable for different user agents. You would
only need to use
- <link href="../userdocs/user/advanced/matchers_selectors.html">matchers
+ <link href="../userdocs/concepts/matchers_selectors.html">matchers
and selectors</link> and to choose the appropriate transformation.
We hope this how-to was helpful for you.
</p>
1.3 +0 -0 cocoon-2.1/src/documentation/xdocs/developing/deliquick.xml
1.5 +0 -0 cocoon-2.1/src/documentation/xdocs/developing/extending.xml
1.3 +0 -0 cocoon-2.1/src/documentation/xdocs/developing/parent-component-manager.xml
1.3 +0 -0 cocoon-2.1/src/documentation/xdocs/developing/datasources.xml
1.4 +1 -0 cocoon-2.1/src/documentation/xdocs/developing/book.xml
1.4 +0 -0 cocoon-2.1/src/documentation/xdocs/developing/httprequest.xml
1.3 +0 -0 cocoon-2.1/src/documentation/xdocs/developing/deli.xml
1.1 cocoon-2.1/src/documentation/xdocs/developing/source.xml
Index: source.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<document>
<header>
<title>Cocoon Source Resolving</title>
<authors>
<person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
</authors>
</header>
<body>
<section>
<title>Differences between Cocoon and Avalon Excalibur Source Resolving</title>
<p>
This story tries to list the changes between the two source resolving approaches.
Originally, the source resolving was developed in the Cocoon community. As the
community recognized that it had a more common value, the source resolving was
donated to the Avalon Excalibur project and there it was refined and redesigned.
Now the way back takes place by reintegrating the Avalon Excalibur Source Resolving
into Cocoon and deprecating the now obsolete Cocoon Source Resolving.</p>
<section>
<title>The Interfaces</title>
<p>
Besides the package names the main difference is that the Cocoon Source object is
XMLizable, that means it can directly send SAX events.
The AE Source object is not XMLizable, which is more correct as a protocol only
describes the way of transport but not the format of the data which is transfered.
Therefore it provides a getMimeType() method.</p>
</section>
<section>
<title>Caching</title>
<p>
The Cocoon Source object returns a last modified time stamp which is very limiting.
For example a source could have an expires date or something like that.
The AE Source returns a validity object which is capable of all these validity
checkings. So the information used for validity checking is provided by the source
object and not maintained by the client of the source as it is currently in Cocoon.</p>
</section>
<section>
<title>XMLizable</title>
<p>
As we in Cocoonland are dealing a lot with XML, a Source implementation can still implement
the XMLizable Interface (from AE and not from Cocoon!) to directly provide SAX events.
The Cocoon SourceUtil class has a method toSAX() which gets a Source object and tests if
it implements the XMLizable interface. If not the new AE XMLizer is used which is a
component that can convert an input stream with a given mime-type to SAX events.
This component is configurable and extensible.</p>
</section>
</section>
</body>
</document>
1.5 +0 -0 cocoon-2.1/src/documentation/xdocs/developing/web3.xml
1.4 +14 -0 cocoon-2.1/src/documentation/xdocs/developing/index.xml
1.5 +33 -12 cocoon-2.1/src/documentation/xdocs/developing/avalon.xml
1.4 +1 -1 cocoon-2.1/src/documentation/xdocs/faq/faq-generators.xml
Index: faq-generators.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/faq/faq-generators.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- faq-generators.xml 3 Sep 2003 08:01:34 -0000 1.3
+++ faq-generators.xml 12 Oct 2003 13:31:54 -0000 1.4
@@ -15,7 +15,7 @@
In the sitemap file, each generator has a unique name which is mapped to a java class. One generator name must be declared as the default generator. Each generator may have additional configuration information specified in child elements.
</p>
<p>
-For conceptual information on generators see the user's guide document <link href="../userdocs/user/sitemap/preface.html">The Sitemap</link>. For detailed descriptions about all of the available Cocoon generators, see the user's guide document <link href="../userdocs/user/sitemap/sitemap.html">Generators in Cocoon</link>. You may also wish to consult the Cocoon API documentation.
+For conceptual information on generators see the user's guide document <link href="../userdocs/concepts/sitemap.html">The Sitemap</link>. For detailed descriptions about all of the available Cocoon generators, see the user's guide document <link href="../userdocs/concepts/sitemap.html">Generators in Cocoon</link>. You may also wish to consult the Cocoon API documentation.
</p>
</answer>
</faq>
1.5 +2 -2 cocoon-2.1/src/documentation/xdocs/faq/faq-matchers.xml
Index: faq-matchers.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/faq/faq-matchers.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- faq-matchers.xml 2 Sep 2003 13:53:10 -0000 1.4
+++ faq-matchers.xml 12 Oct 2003 13:31:54 -0000 1.5
@@ -19,7 +19,7 @@
In the sitemap file, each matcher has a unique name which is mapped to a java class. One matcher name must be declared as the default matcher. Each matcher may have additional configuration information specified in child elements.
</p>
<p>
- For more conceptual information about matchers see <link href="../userdocs/user/advanced/matchers_selectors.html">Using and Implementing Matchers and Selectors</link>. For detailed descriptions about all of the available Cocoon matchers, see the user's guide document <link href="../userdocs/components/matchers/matchers.html">Matchers in Cocoon</link>. You may also wish to consult the Cocoon API documentation.
+ For more conceptual information about matchers see <link href="../userdocs/concepts/matchers_selectors.html">Using and Implementing Matchers and Selectors</link>. For detailed descriptions about all of the available Cocoon matchers, see the user's guide document <link href="../userdocs/matchers/matchers.html">Matchers in Cocoon</link>. You may also wish to consult the Cocoon API documentation.
</p>
</answer>
@@ -32,7 +32,7 @@
<answer>
<p>
-Both matchers and selectors can be used to determine the flow, order, and components involved in request processing. Their differences include the complexity of the decisions they can make about processing as well as the values they return to the sitemap. For a more detailed discussion of their similarities and differences, see <link href="../userdocs/user/advanced/matchers_selectors.html">Using and Implementing Matchers and Selectors</link>.
+Both matchers and selectors can be used to determine the flow, order, and components involved in request processing. Their differences include the complexity of the decisions they can make about processing as well as the values they return to the sitemap. For a more detailed discussion of their similarities and differences, see <link href="../userdocs/concepts/matchers_selectors.html">Using and Implementing Matchers and Selectors</link>.
</p>
</answer>
1.5 +2 -2 cocoon-2.1/src/documentation/xdocs/faq/faq-transformers.xml
Index: faq-transformers.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/faq/faq-transformers.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- faq-transformers.xml 3 Sep 2003 07:19:09 -0000 1.4
+++ faq-transformers.xml 12 Oct 2003 13:31:54 -0000 1.5
@@ -16,7 +16,7 @@
In the sitemap file, each transformer has a unique name which is mapped to a java class. One transformer name must be declared as the default transformer. Each transformer may have additional configuration information specified in child elements.
</p>
<p>
- For more conceptual information about transformers see <link href="../userdocs/user/sitemap/preface.html">the sitemap</link>. For detailed descriptions about all of the available Cocoon transformers, see the user's guide document <link href="../userdocs/components/transformers/transformers.html">Transformers in Cocoon</link>. You may also wish to consult the Cocoon API documentation.
+ For more conceptual information about transformers see <link href="../userdocs/concepts/sitemap.html">the sitemap</link>. For detailed descriptions about all of the available Cocoon transformers, see the user's guide document <link href="../userdocs/transformers/transformers.html">Transformers in Cocoon</link>. You may also wish to consult the Cocoon API documentation.
</p>
</answer>
@@ -54,7 +54,7 @@
</ul>
<p>
-Consult the user documentation for more information about the <link href="../userdocs/components/transformers/xinclude-transformer.html">XIncludeTransformer</link> and <link href="../userdocs/components/transformers/cinclude-transformer.html">CIncludeTransformer</link>. Please note that an IncludeTransformer, with support for both cinclude and xinclude as well as a configurable namespace, is planned for a future release.
+Consult the user documentation for more information about the <link href="../userdocs/transformers/xinclude-transformer.html">XIncludeTransformer</link> and <link href="../userdocs/transformers/cinclude-transformer.html">CIncludeTransformer</link>. Please note that an IncludeTransformer, with support for both cinclude and xinclude as well as a configurable namespace, is planned for a future release.
</p>
</answer>
1.4 +2 -2 cocoon-2.1/src/documentation/xdocs/faq/faq-configure-environment.xml
Index: faq-configure-environment.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/faq/faq-configure-environment.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- faq-configure-environment.xml 2 Sep 2003 13:17:34 -0000 1.3
+++ faq-configure-environment.xml 12 Oct 2003 13:31:54 -0000 1.4
@@ -181,7 +181,7 @@
The "file:" type of source instructs Cocoon to search the sub-sitemap
under the specified directory (which happens to be "c:\foo", since this
is a Windows system). See explanation of
- <link href="../userdocs/user/sitemap/sitemap.html#file-url">file: URLs</link>
+ <link href="../userdocs/concepts/sitemap.html#file-url">file: URLs</link>
</p>
<p>
Now, you just need to copy everything which was under the
@@ -267,7 +267,7 @@
<p>
Another solution is to use PJA library. Read 'Linux/Headless/Batik'
- section in the <link href="../userdocs/installation/index.html">Cocoon installation guide</link>.
+ section in the <link href="../installing/index.html">Cocoon installation guide</link>.
</p>
</answer>
</faq>
1.4 +1 -1 cocoon-2.1/src/documentation/xdocs/faq/faq-serializers.xml
Index: faq-serializers.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/faq/faq-serializers.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- faq-serializers.xml 2 Sep 2003 12:56:17 -0000 1.3
+++ faq-serializers.xml 12 Oct 2003 13:31:54 -0000 1.4
@@ -16,7 +16,7 @@
In the sitemap file, each serializer has a unique name which is mapped to a java class. One serializer name must be declared as the default serializer. Each serializer may have additional configuration information specified in child elements.
</p>
<p>
- For more conceptual information about serializers see <link href="../userdocs/user/sitemap/preface.html">the sitemap</link>. For detailed descriptions about all of the available Cocoon serializers, see the user's guide document <link href="../userdocs/components/serializers/serializers.html">Serializers in Cocoon</link>. You may also wish to consult the Cocoon API documentation.
+ For more conceptual information about serializers see <link href="../userdocs/concepts/sitemap.html">the sitemap</link>. For detailed descriptions about all of the available Cocoon serializers, see the user's guide document <link href="../userdocs/serializers/serializers.html">Serializers in Cocoon</link>. You may also wish to consult the Cocoon API documentation.
</p>
</answer>
</faq>
1.3 +1 -1 cocoon-2.1/src/documentation/xdocs/faq/faq-sitemap.xml
Index: faq-sitemap.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/faq/faq-sitemap.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- faq-sitemap.xml 2 Sep 2003 12:56:17 -0000 1.2
+++ faq-sitemap.xml 12 Oct 2003 13:31:54 -0000 1.3
@@ -227,7 +227,7 @@
</ul>
<p>
See further explanation of
- <link href="../userdocs/user/sitemap/sitemap.html#file-url">file: URLs</link>
+ <link href="../userdocs/concepts/sitemap.html#file-url">file: URLs</link>
</p>
</answer>
</faq>
1.5 +2 -2 cocoon-2.1/src/documentation/xdocs/faq/faq-selectors.xml
Index: faq-selectors.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/faq/faq-selectors.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- faq-selectors.xml 3 Sep 2003 08:01:34 -0000 1.4
+++ faq-selectors.xml 12 Oct 2003 13:31:54 -0000 1.5
@@ -17,7 +17,7 @@
In the sitemap file, each selector has a unique name which is mapped to a java class. One selector name must be declared as the default selector. Each selector may have additional configuration information specified in child elements.
</p>
<p>
- For more conceptual information about selectors see <link href="../userdocs/user/advanced/matchers_selectors.html">Using and Implementing Matchers and Selectors</link>. For detailed descriptions about all of the available Cocoon selectors, see the user's guide document <link href="../userdocs/components/selectors/selectors.html">Matchers in Cocoon</link>. You may also wish to consult the Cocoon API documentation.
+ For more conceptual information about selectors see <link href="../userdocs/concepts/matchers_selectors.html">Using and Implementing Matchers and Selectors</link>. For detailed descriptions about all of the available Cocoon selectors, see the user's guide document <link href="../userdocs/selectors/selectors.html">Matchers in Cocoon</link>. You may also wish to consult the Cocoon API documentation.
</p>
</answer>
@@ -30,7 +30,7 @@
<answer>
<p>
-Both matchers and selectors can be used to determine the flow, order, and components involved in request processing. Their differences include the complexity of the decisions they can make about processing as well as the values they return to the sitemap. For a more detailed discussion of their similarities and differences, see <link href="../userdocs/user/advanced/matchers_selectors.html">Using and Implementing Matchers and Selectors</link>.
+Both matchers and selectors can be used to determine the flow, order, and components involved in request processing. Their differences include the complexity of the decisions they can make about processing as well as the values they return to the sitemap. For a more detailed discussion of their similarities and differences, see <link href="../userdocs/concepts/matchers_selectors.html">Using and Implementing Matchers and Selectors</link>.
</p>
</answer>
1.6 +4 -5 cocoon-2.1/src/documentation/xdocs/installing/book.xml
1.20 +0 -0 cocoon-2.1/src/documentation/xdocs/installing/updating.xml
1.1 cocoon-2.1/src/documentation/xdocs/installing/requirements.xml
Index: requirements.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="../css/document.css"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "../dtd/document-v10.dtd">
<document>
<header>
<title>Installing Apache Cocoon</title>
<authors>
<person name="Stefano Mazzocchi" email="stefano@apache.org"/>
<person name="Giacomo Pati" email="Giacomo.Pati@pwr.ch"/>
<person name="Tom Klaasen" email="tom.klaasen@pandora.be"/>
<person name="Chris Stevenson" email="zhcchz@mail.on.net"/>
<person name="Carsten Ziegeler" email="cziegeler@apache.org"/>
<person name="Vadim Gritsenko" email="vgritsenko@apache.org"/>
<person name="Bernhard Huber" email="berni_huber@a1.net"/>
<person name="Nicola Ken Barozzi" email="nicolaken@apache.org"/>
<person name="Sylvain Wallez" email="sylvain@apache.org"/>
</authors>
</header>
<body>
<s1 title="System Requirements">
<p>
Apache Cocoon requires the following systems to be already installed in your system:
</p>
<p><strong>Java Virtual Machine</strong>
A Java 1.3 or later compatible virtual machine must be present for both
command line and servlet type usage of Apache Cocoon. Note that all servlet engines
require a JVM to run so if you are already using servlets you already have
one installed.
</p>
<p><strong>Servlet Engine</strong>
A Servlet 2.2 compliant servlet engine must be present in order to support
servlet operation and dynamic request handling. Note that this requirement
is optional for command line operation. Note also that Cocoon now ships
with a stripped down version of Jetty suitable for immediately testing
with no further downloads.
</p>
<p>When the time comes to run your Cocoon application in a full featured
servlet container, you may want to consider the following Open Source
options:</p>
<ol>
<li>The Apache Tomcat project
<link href="http://jakarta.apache.org/tomcat/">http://jakarta.apache.org/tomcat/</link>
</li>
<li>The full version of Jetty
<link href="http://jetty.mortbay.org/">http://jetty.mortbay.org/</link>
</li>
</ol>
</s1>
</body>
</document>
1.3 +0 -0 cocoon-2.1/src/documentation/xdocs/installing/tests.xml
1.4 +0 -0 cocoon-2.1/src/documentation/xdocs/installing/jars.xml
1.11 +0 -33 cocoon-2.1/src/documentation/xdocs/installing/index.xml
1.5 +4 -4 cocoon-2.1/src/documentation/xdocs/plan/changes-doc.xml
Index: changes-doc.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/plan/changes-doc.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- changes-doc.xml 27 Sep 2003 12:55:25 -0000 1.4
+++ changes-doc.xml 12 Oct 2003 13:31:55 -0000 1.5
@@ -80,9 +80,9 @@
<link href="../faq/faq-xsp.html">XSP</link>.
</action>
<action dev="DS" type="update">
- Edited <link href="../userdocs/components/matchers/matchers.html">Matchers</link>,
- <link href="../userdocs/components/selectors/selectors.html">Selectors</link>, and a number
- of other user guide doc files to address grammar, typos, and general Global English issues.
+ Edited <link href="../userdocs/matchers/matchers.html">Matchers</link>,
+ <link href="../userdocs/selectors/selectors.html">Selectors</link>, and a number of other
+ user guide doc files to address grammar, typos, and general Global English issues.
</action>
<action dev="DS" type="update">
Added stylesheet, src/documentation/stylesheets/faqcommon.xsl, which places two