forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r514566 - in /forrest/trunk/site-author/content/xdocs: ./ docs_0_80/ docs_0_80/howto/ docs_0_80/howto/cvs-ssh/ pluginDocs/ pluginDocs/plugins_0_80/ procedures/release/ versions/
Date Mon, 05 Mar 2007 06:32:19 GMT
Author: crossley
Date: Sun Mar  4 22:32:17 2007
New Revision: 514566

Remove "v0.80" from "site:" references. In the absence of a version qualifier,
it will use the first match that it finds in site.xml (i.e. the current version,
which is exactly what we want). When we move to the next version of Forrest,
these references will now work automatically.
This solves a fixme note in the "How_to_release" doc.


Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/build.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/build.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/build.xml Sun Mar  4 22:32:17 2007
@@ -103,7 +103,7 @@
       content/xdocs/*.xml see the immediate effect.
-      The document <link href="site:v0.80//your-project">Using Forrest</link> is
+      The document <link href="site:your-project">Using Forrest</link> is
       your next step.</p>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/catalog.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/catalog.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/catalog.xml Sun Mar  4 22:32:17 2007
@@ -236,7 +236,7 @@
         Other Forrest documentation has some notes about configuring the
         entity resolver for your own DTDs. See
-        <link href="site:v0.80//validation">XML Validation</link>.
+        <link href="site:validation">XML Validation</link>.
         Cocoon has extensive documentation about the entity resolver. See

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/dreams.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/dreams.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/dreams.xml Sun Mar  4 22:32:17 2007
@@ -30,7 +30,7 @@
   <p>This is the initial attempt to give focus to the Forrest project. 
    This summary is a loose collection of items from the forrest-dev
    mailing list. Please add and re-arrange so that it can evolve into a
-   focus document. The <link href="site:v0.80//primer">Forrest Primer</link>
+   focus document. The <link href="site:primer">Forrest Primer</link>
    provides an overview.

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/faq.xml Sun Mar  4 22:32:17 2007
@@ -33,7 +33,7 @@
     <faq id="overview">
       <question> Where can I read an overview about how to work with Forrest? </question>
-        <p> See the <link href="site:v0.80//your-project">Using Forrest</link> guide. </p>
+        <p> See the <link href="site:your-project">Using Forrest</link> guide. </p>
     <faq id="requirements">
@@ -60,8 +60,8 @@
     <faq id="svn">
       <question> How can I use SVN to keep up to date with the latest codebase? </question>
-        <p> Follow these <link href="site:v0.80//build">Building Forrest</link> notes. </p>
-        <p> The <link href="site:v0.80//your-project">Using Forrest</link> guide provides further
+        <p> Follow these <link href="site:build">Building Forrest</link> notes. </p>
+        <p> The <link href="site:your-project">Using Forrest</link> guide provides further
           step-by-step assistance in getting started with Forrest for your project. </p>
@@ -72,7 +72,7 @@
           Sometimes one does not want to use the most recent functionality
           of a plugin and instead need to use an older version.
           Information about changes to each plugin can be found in its
-          <link href="site:v0.80//plugins/index">documentation</link>.
+          <link href="site:plugins/index">documentation</link>.
           In the file, specify the version of the plugin
@@ -185,9 +185,9 @@
     <faq id="edit-content">
       <question>What tools can be used to edit the content?</question>
-        <p>If you are using the Apache Forrest XML <link href="site:v0.80//dtd-docs">document format</link>
+        <p>If you are using the Apache Forrest XML <link href="site:dtd-docs">document format</link>
           or DocBook or other XML document types, then you can use any text editor or even a
-          dedicated XML editor. You must ensure valid XML. See our <link href="site:v0.80//catalog"
+          dedicated XML editor. You must ensure valid XML. See our <link href="site:catalog"
             >configuration notes</link> for various editors. </p>
         <p>There are content management systems like <link href="ext:lenya">Apache Lenya</link>. </p>
         <p>Remember that Forrest can also use other source formats, such as docs or
@@ -207,7 +207,7 @@
           defining the navigation menus, and as a method for defining references
           to be used when linking between documents.
           This file is fully explained in
-          <link href="site:v0.80//linking">Menus and Linking</link>. Here is a precis:
+          <link href="site:linking">Menus and Linking</link>. Here is a precis:
           The labels can be whatever text you want.
@@ -286,9 +286,9 @@
         <p> In this case the menu labeled "About" will have 2 new items: "Full PDF" and "Full HTML".
-          (See also <link href="site:v0.80//pdf-tab">How to create a PDF document for each
+          (See also <link href="site:pdf-tab">How to create a PDF document for each
           tab</link>.) </p>
-        <p> This assumes that you use the <link href="site:v0.80//linking">site.xml</link> method for your
+        <p> This assumes that you use the <link href="site:linking">site.xml</link> method for your
           site structure and navigation, rather than the old book.xml method. </p>
@@ -379,7 +379,7 @@
       <question>I need help with the interaction between tabs.xml and site.xml </question>
-          See the <link href="site:v0.80//linking/tab-site">tips</link>.
+          See the <link href="site:linking/tab-site">tips</link>.
@@ -394,7 +394,7 @@
           <li> Edit that file to replace 'index.html' in
             with 'overview.html'. </li>
-          <li> Edit your project's <link href="site:v0.80//project-sitemap">sitemap.xmap</link> file. </li>
+          <li> Edit your project's <link href="site:project-sitemap">sitemap.xmap</link> file. </li>
           <li> Add the following code just before the end of the pipelines-element:<source><![CDATA[
     <map:match type="regexp" pattern="^.+/$">
@@ -415,7 +415,7 @@
           start-up-page for a CD-based documentation project to be named 'start.html'. </p>
         <p>To change the start page of a site:</p>
-          <li>Edit your project's <link href="site:v0.80//project-sitemap">sitemap.xmap</link> file.</li>
+          <li>Edit your project's <link href="site:project-sitemap">sitemap.xmap</link> file.</li>
           <li>Add the following code just before the end of the pipelines-element:<source><![CDATA[
     <map:match pattern="">
@@ -645,7 +645,7 @@
         <p>If you have:<code>&#60;version&#62;$Revision: 1.30
           $&#60;/version&#62;</code>The &#39;1.30&#39; will be extracted and
           displayed at the bottom of the page as &#34;version 1.30&#34;. See for example the
-          bottom of the <link href="site:v0.80//your-project"> Using Forrest</link> document.</p>
+          bottom of the <link href="site:your-project"> Using Forrest</link> document.</p>
         <p>This technique could also be used for a modification date with $Date: 2004/01/15 08:52:47
@@ -678,7 +678,7 @@
         <p>This is just an example, and you should modify it appropriately for your site.</p>
         <note> Wildcards may be used. These are a powerful feature of Cocoon's <link
-            href="site:v0.80//sitemap-ref">sitemap</link>. For example, <strong>foo/*</strong> would match
+            href="site:sitemap-ref">sitemap</link>. For example, <strong>foo/*</strong> would match
             <code>foo/bar</code>, but not <code>foo/bar/baz</code> &mdash; use
           <strong>foo/**</strong> to match that. </note>
@@ -762,19 +762,19 @@
       <question> How do i configure my favourite XML editor or parser to find the local Forrest
         DTDs? </question>
-        <p> Notes are provided for various tools at <link href="site:v0.80//catalog">Using Catalog Entity
+        <p> Notes are provided for various tools at <link href="site:catalog">Using Catalog Entity
             Resolver for local DTDs</link>. </p>
     <faq id="skin">
       <question> How to make the site look better and change its skin? </question>
-        <p> There are <link href="site:v0.80//skins">default skins</link> provided, which are configurable
+        <p> There are <link href="site:skins">default skins</link> provided, which are configurable
           and so should meet the needs of most projects. The aim is to provide many capabilities so
           that extra skins are not needed. </p>
-        <p> See notes about <link href="site:v0.80//your-project/skins">configuration</link> of the skins.
+        <p> See notes about <link href="site:your-project/skins">configuration</link> of the skins.
           Some projects may have special needs and can define their <link
-            href="site:v0.80//your-project/new-skin">own skin</link>. </p>
+            href="site:your-project/new-skin">own skin</link>. </p>
     <faq id="xsp">
@@ -791,7 +791,7 @@
             directory (or lib/core/ directory in the source distribution).</li>
             <p> Add the following generator definition in the map:generators section of your <link
-                href="site:v0.80//project-sitemap">project sitemap</link>
+                href="site:project-sitemap">project sitemap</link>
   <map:generator name="serverpages"
@@ -911,7 +911,7 @@
           files. However, Forrest first checks for the existence of a book.xml file, so
           backwards-compatibility is preserved. If a directory has a book.xml file, the book.xml
           will be used to generate the menu. This supplement is useful in situations where
-          &s;-generated menus aren't appropriate. See <link href="site:v0.80//linking">Menus and
+          &s;-generated menus aren't appropriate. See <link href="site:linking">Menus and
             Linking</link>. </p>
@@ -926,8 +926,8 @@
         <p> The other way is to use the full DocBook stylesheets directly. The DocBook DTDs are
           shipped with Forrest and automatically handled. However, you will need to have the DocBook
           stylesheets on your system (they are too massive to ship with Forrest) and configure
-          Forrest accordingly. You will need to create a <link href="site:v0.80//project-sitemap">project
-            sitemap</link> as explained in <link href="site:v0.80//your-project">Using Forrest</link> and
+          Forrest accordingly. You will need to create a <link href="site:project-sitemap">project
+            sitemap</link> as explained in <link href="site:your-project">Using Forrest</link> and
           add matches to handle your DocBook documents. Here is an example. Note that you need to
           change it to suit your situation. The match must be very specific so that only the DocBook
           documents are matched. The rest of the documents will be handled by Forrest core. Powerful
@@ -960,7 +960,7 @@
           html, then uses a Forrest core stylesheet to transform and serialize
           to the internal xml format, then the normal machinery takes over and
           does the output transformation. This use the Content Aware Pipelines
-          (<link href="site:v0.80//cap">SourceTypeAction</link>)
+          (<link href="site:cap">SourceTypeAction</link>)
           to peek at the source xml. If it is DocBook-4.2
           then this sitemap match is triggered, if not then it falls through to the core of Forrest.
@@ -1005,7 +1005,7 @@
           "document-v*" DTD and DocBook. </p>
         <p> Ensure that the document type declaration in your XML instance is well specified. Use a
           public identifier. The DTD will then be properly resolved by Forrest. If you need to use
-          different DTDs, then see <link href="site:v0.80//your-project/new_dtd">Using Forrest</link> for
+          different DTDs, then see <link href="site:your-project/new_dtd">Using Forrest</link> for
           configuration guidance. </p>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/cvs-ssh/book.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/cvs-ssh/book.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/cvs-ssh/book.xml Sun Mar  4 22:32:17 2007
@@ -23,7 +23,7 @@
   <menu label="How-To Samples">
-    <menu-item label="Overview" href="site:v0.80//overview"/>
+    <menu-item label="Overview" href="site:overview"/>
   <menu label="Committers">
     <menu-item label="CVS through SSH" href="howto-cvs-ssh.html"/>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml Sun Mar  4 22:32:17 2007
@@ -218,7 +218,7 @@
       <p>It is beyond the scope of this How-To to give details about how to 
       build your plugins XMap. See the 
-      <a href="site:v0.80//sitemap-ref">Sitemap Reference</a> for general
+      <a href="site:sitemap-ref">Sitemap Reference</a> for general
       information. See also 
       <a href="site:plugins/infrastructure">Plugin Infrastructure</a>
       for some hints and tips on creating plugin sitemaps. In addition, as with

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-corner-images.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-corner-images.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-corner-images.xml Sun Mar  4 22:32:17 2007
@@ -52,8 +52,8 @@
       <li>Understand how to use the skinconf.xml file to change the appearance
       of the output documents.</li>
       <li>Understand how to create or modify skins by following the
-      <a href="site:v0.80//your-project">Using Forrest</a> document
-       (topic "<a href="site:v0.80//your-project/skins">Forrest skins</a>").</li>
+      <a href="site:your-project">Using Forrest</a> document
+       (topic "<a href="site:your-project/skins">Forrest skins</a>").</li>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-custom-html-source.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-custom-html-source.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-custom-html-source.xml Sun Mar  4 22:32:17 2007
@@ -47,7 +47,7 @@
         Know how to use a
-        <a href="site:v0.80//project-sitemap">project sitemap</a>.
+        <a href="site:project-sitemap">project sitemap</a>.
         A basic understanding of coocons pipelines and their

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-pdf-tab.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-pdf-tab.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-pdf-tab.xml Sun Mar  4 22:32:17 2007
@@ -46,7 +46,7 @@
   <prerequisites title="Prerequisites">
       <li>Understand how to create project-specific sitemaps by following the
-      <link href="site:v0.80//your-project">Using Forrest</link> document.</li>
+      <link href="site:your-project">Using Forrest</link> document.</li>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/index.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/index.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/index.xml Sun Mar  4 22:32:17 2007
@@ -31,7 +31,7 @@
           - Provides instructions about writing documents. Please copy this
           file to serve as a template for your own document.
-        <li><link href="site:v0.80//asf-mirror">Generate an ASF mirrors page using interactive web form</link>
+        <li><link href="site:asf-mirror">Generate an ASF mirrors page using interactive web form</link>
           - include html form elements
           into a forrest-generated html page. For example, this enables building
           automated download mirror pages for ASF project websites.
@@ -48,24 +48,24 @@
         users and developers.
-        <li><link href="site:v0.80//pdf-tab">How to create a PDF document for each tab</link>
+        <li><link href="site:pdf-tab">How to create a PDF document for each tab</link>
           - Describes the generation of a PDF document for each
           group of documents that is defined by a tab.
-        <li><link href="site:v0.80//editcss">How to edit Forrest's CSS in a WYSIWYG fashion</link>
+        <li><link href="site:editcss">How to edit Forrest's CSS in a WYSIWYG fashion</link>
           - Describes the use of Mozilla Firebird and the free EditCSS-Plugin to 
           customize your Forrest design in a WYSIWYG-way.
-        <li><link href="site:v0.80//corner-css">How to modify the color of generated corner images</link>
+        <li><link href="site:corner-css">How to modify the color of generated corner images</link>
           - Describes the use of CSS values from the skinconf.xml configuration
           file to change the color of the corner images to be suitable for
           your own skin colors. Advanced use explains editing the *.css too.
-        <li><link href="site:v0.80//maven">How to run Forrest from within Maven</link>
+        <li><link href="site:maven">How to run Forrest from within Maven</link>
         - For Maven users who want to generate their project's documentation and/or website
           using Forrest in lieu of Maven's site plugin.
-        <li><link href="site:v0.80//custom-html-source">How to customize processing of html source</link>
+        <li><link href="site:custom-html-source">How to customize processing of html source</link>
         - When integrating legacy html documents into a Forrest-built site, additional processing
         of the html sources might be required.
@@ -75,7 +75,7 @@
       <title>Extending Forrest</title>
-        <li><link href="site:v0.80//buildPlugin">How to create a Plugin for Forrest</link>
+        <li><link href="site:buildPlugin">How to create a Plugin for Forrest</link>
           - Describes how to write a plugin to add new input or output document
           formats, or to modify the default behaviour of Forrest</li>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/linking.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/linking.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/linking.xml Sun Mar  4 22:32:17 2007
@@ -69,7 +69,7 @@
         <dd>&s; is used to generate the menus for the HTML website.</dd>
         <dt><link href="#indirect-linking">Indirect linking</link></dt>
         <dd>&s; provides a basic aliasing mechanism for linking, e.g. one
-          can write &lt;link href="site:v0.80//changes"> from anywhere in the site, and
+          can write &lt;link href="site:changes"> from anywhere in the site, and
           link to the "changes" information node (translated to changes.html).
           More on this below.</dd>
@@ -150,7 +150,7 @@
-        See another <link href="site:v0.80//faq/site-xml">explained example</link>.
+        See another <link href="site:faq/site-xml">explained example</link>.
@@ -357,7 +357,7 @@
             is present in the linked-to directory. How do I fix this?
             A: In &t; use @href instead of @dir attribute and omit the trailing '/'.
             Which file to serve is then a concern of the sitemap.
-            See more at the <link href="site:v0.80//faq/tab-index">FAQ</link>.
+            See more at the <link href="site:faq/tab-index">FAQ</link>.
@@ -425,7 +425,7 @@
         <title>Indirect linking</title>
           Forrest's solution is simple: instead of &lt;a href="todo.html">,
-          write &lt;a href="site:v0.80//todo"> where:
+          write &lt;a href="site:todo"> where:
@@ -448,7 +448,7 @@
           <title>Resolving site: URIs</title>
-            So how does "<code>site:v0.80//todo</code>" get resolved?  A full answer
+            So how does "<code>site:todo</code>" get resolved?  A full answer
             is provided in the <link href="#implementation">implementation</link>
             section.  Essentially, the "<code>todo</code>" part has
             "<code>/site//</code>" prepended, and "<code>/@href</code>" appended, to
@@ -468,7 +468,7 @@
             Notice that the "//" allows us any degree of specificity when linking.
-            In the sample &s; above, both "<code>site:v0.80//new_content_type</code>" and
+            In the sample &s; above, both "<code>site:new_content_type</code>" and
             "<code>site:about/your-project/new_content_type</code>" identify the
             same node.  It is up to you to decide how specific to make links.  One
             nice benefit of link "ambiguity" is that &s; can be reorganized
@@ -519,7 +519,7 @@
         <section id="source-uris">
           <title>Theory: source URIs</title>
-            The "<code>site:</code>" URIs like "<code>site:v0.80//todo</code>" are examples of
+            The "<code>site:</code>" URIs like "<code>site:todo</code>" are examples of
             "<em>source</em>" URIs, in contrast to the more usual
             <code>foo.html</code> style URIs, which we here call
             "<em>destination</em>" URIs.  This introduces an important concept: that
@@ -606,9 +606,9 @@
     <section id="implementation">
       <p>Full details on the implementation of
-      <link href="site:v0.80//linkrewriting_impl">link rewriting</link> and
-      <link href="site:v0.80//menu_generation_impl">menu generation</link> are available in
-      the <link href="site:v0.80//sitemap-ref">Sitemap Reference</link></p>
+      <link href="site:linkrewriting_impl">link rewriting</link> and
+      <link href="site:menu_generation_impl">menu generation</link> are available in
+      the <link href="site:sitemap-ref">Sitemap Reference</link></p>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/primer.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/primer.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/primer.xml Sun Mar  4 22:32:17 2007
@@ -432,7 +432,7 @@
         them to start contributing to Forrest. We have a decent generation system for
         static project documentation, a nice set of skins and some simple but effective
         DTDs. Our goals however are much more ambitious: we have compiled a
-        <link href="site:v0.80//dreams">dream list</link> that lists most of them.</p> 
+        <link href="site:dreams">dream list</link> that lists most of them.</p> 
         <li>Our first ambition is to support the project site generation and
           maintenance of other Apache projects in an automated manner, starting with our

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/project-sitemap.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/project-sitemap.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/project-sitemap.xml Sun Mar  4 22:32:17 2007
@@ -36,7 +36,7 @@
         and related component documentation.
         The Forrest sitemap is broken into multiple files. The main one is
         <strong>sitemap.xmap</strong> which delegates to others.  See the
-         <link href="site:v0.80//sitemap-ref">Sitemap Reference</link> for a tour of the
+         <link href="site:sitemap-ref">Sitemap Reference</link> for a tour of the
         default sitemap.
@@ -71,9 +71,9 @@
         <title>Adding a new content type</title>
           See the section "Advanced customizations: sitemap.xmap" in
-          the <link href="site:v0.80//your-project">Using Forrest</link> document
+          the <link href="site:your-project">Using Forrest</link> document
           and then follow the
-          <link href="site:v0.80//your-project/new_content_type">Example:
+          <link href="site:your-project/new_content_type">Example:
           Adding a new content type</link>.

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/sitemap-ref.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/sitemap-ref.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/sitemap-ref.xml Sun Mar  4 22:32:17 2007
@@ -60,7 +60,7 @@
         is not handled, passes through to be handled by the default Forrest
         sitemaps - obviously extremely powerful. The capability is described
-        "<link href="site:v0.80//project-sitemap">Using project sitemaps</link>".
+        "<link href="site:project-sitemap">Using project sitemaps</link>".
@@ -102,7 +102,7 @@
           <td>Defines a mapping from abstract ("site:index") to physical
             ("index.html") links for the current page.  See 
-            <link href="site:v0.80//linking">Menus and Linking</link> for a conceptual
+            <link href="site:linking">Menus and Linking</link> for a conceptual
             overview, and the <link href="#linkrewriting_impl">Link
               rewriting</link> section for technical details.</td>
@@ -126,7 +126,7 @@
-          <td>Generates <link href="site:v0.80//changes">changes</link> and 
+          <td>Generates <link href="site:changes">changes</link> and 
           <link href="site:todo">todo</link> pages from a single
             <code>status.xml</code> in the project root.
@@ -151,7 +151,7 @@
             <link href="">DTD
               Parser</link>.  Useful for documenting DTD-based XML schemas, such
-            as <link href="site:v0.80//dtd-docs">Forrest's own DTDs</link>.
+            as <link href="site:dtd-docs">Forrest's own DTDs</link>.
@@ -218,7 +218,7 @@
           Most of the usual Source pipelines are defined in
           <code>forrest.xmap</code> which is the default (fallback) handler for
           <code>**.xml</code> pages. The forrest.xmap uses the 
-          <link href="site:v0.80//cap">SourceTypeAction</link> to determine the type of XML
+          <link href="site:cap">SourceTypeAction</link> to determine the type of XML
           it is processing, and converts it to document-v13 if necessary.
         <p>For instance, say we are rendering <link href="site:write-howto">a
@@ -500,7 +500,7 @@
       <p>Meaning that it is defined in the <code>menu.xmap</code> file.  In there we find
         the real definition, which is quite complicated, because there are three
-        supported menu systems (see <link href="site:v0.80//linking">menus and
+        supported menu systems (see <link href="site:linking">menus and
           linking</link>).  We will not go through the sitemap itself
         (menu.xmap), but will instead describe the logical steps involved:</p>
@@ -508,7 +508,7 @@
         <li><p>Depending on the <code></code> property, we
             now apply one of the two algorithms for choosing a set of menu links
-            (described in <link href="site:v0.80//menu_generation">menu
+            (described in <link href="site:menu_generation">menu
@@ -574,7 +574,7 @@
         "linkrewriter" transformer in action.  For example:</p>
       <source><![CDATA[<map:transform type="linkrewriter" src="cocoon:/{1}linkmap-{2}.html"/>]]></source>
       <p>This statement is Cocoon's linking system in action.  A full
-        description is provided in <link href="site:v0.80//linking">Menus and
+        description is provided in <link href="site:linking">Menus and
           Linking</link>.  Here we describe the implementation of linking.</p>
       <section id="input_modules">
         <title>Cocoon foundations: Input Modules</title>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/skins.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/skins.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/skins.xml Sun Mar  4 22:32:17 2007
@@ -30,7 +30,7 @@
         Note that the new Dispatcher capability will be a better solution.
-        See <a href="site:v0.80//status-themes">Status of Themes: Skins and Dispatcher</a>.
+        See <a href="site:status-themes">Status of Themes: Skins and Dispatcher</a>.

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/upgrading_08.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/upgrading_08.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/upgrading_08.xml Sun Mar  4 22:32:17 2007
@@ -26,7 +26,7 @@
 This is the <strong>development</strong> version of Apache Forrest which can
 be obtained from the Subversion repository or from a code snapshot.
-See the notes for obtaining and <a href="site:v0.80//build">Building Forrest</a>.
+See the notes for obtaining and <a href="site:build">Building Forrest</a>.
       This page describes some changes to Apache Forrest that affect people who are
@@ -57,7 +57,7 @@
       <p>Many new initial plugins are in the "whiteboard". See the entries in the
         <a href="site:changes">change log</a> and see each plugin's documentation and changes log.
         This includes the new Dispatcher.
-        See <a href="site:v0.80//status-themes">Status of Themes: Skins and Dispatcher</a>.
+        See <a href="site:status-themes">Status of Themes: Skins and Dispatcher</a>.

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/validation.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/validation.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/validation.xml Sun Mar  4 22:32:17 2007
@@ -98,7 +98,7 @@
         as a means of associating public identifiers
         (e.g. <code>-//APACHE//DTD Documentation V1.1//EN</code> above) with DTDs.
-        If you <link href="site:v0.80//new_content_type">add a new content type</link>, you
+        If you <link href="site:your-project/new_content_type">add a new content type</link>, you
         should add the DTD to <code>${project.schema-dir}/dtd/</code> and add
         an entry to the <code>${project.schema-dir}/catalog.xcat</code> file.  This
         section describes the details of this process.
@@ -110,7 +110,7 @@
           The main Forrest DTDs are designed to be modular and extensible, so
           it is fairly easy to create a new document type that is a superset
           of one from Forrest.  This is what we'll demonstrate here, using our
-          earlier <link href="site:v0.80//new_content_type">download format</link>
+          earlier <link href="site:your-project/new_content_type">download format</link>
           as an example.  Our download format adds a group of new elements to
           the standard 'documentv13' format.  Our new elements are described
           by the following DTD:
@@ -342,7 +342,7 @@
         it know where the Forrest catalog file is, and you will be able to
         validate any Forrest XML file, regardless of location, as you edit
         your files. See the 
-        <link href="site:v0.80//catalog">configuration notes</link> your favourite
+        <link href="site:catalog">configuration notes</link> your favourite

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/your-project.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/your-project.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/your-project.xml Sun Mar  4 22:32:17 2007
@@ -38,7 +38,7 @@
        <link href="ext:forrest/download">Download</link> the latest release
        of Forrest and follow the index.html in the top-level, or
        if you want to try the development version, then
-       <link href="site:v0.80//build">build Forrest</link> from source.
+       <link href="site:build">build Forrest</link> from source.
@@ -599,7 +599,7 @@
           <code>site.xml</code> file. This site.xml is like a site index, and is rendered as
           the vertical column of links in the default skin.  Look at Forrest's own
           xdocs for an example.  More detailed info about site.xml is provided in 
-          the document <link href="site:v0.80//linking">Menus and Linking</link>.
+          the document <link href="site:linking">Menus and Linking</link>.
       <section id="tabs.xml">
@@ -608,7 +608,7 @@
           The <code>tabs.xml</code> file is used to produce the 'tabs'.
           which enable users to quickly jump to sections of your site.
           See the
-          <link href="site:v0.80//menu_generation">menu generation</link> documentation
+          <link href="site:menu_generation">menu generation</link> documentation
           for more details, and again, consult Forrest's own docs for a usage
@@ -692,7 +692,7 @@
         is not handled, passes through to be handled by the default Forrest
         sitemaps - obviously extremely powerful. The capability is described
-        "<link href="site:v0.80//project-sitemap">Using project sitemaps</link>"
+        "<link href="site:project-sitemap">Using project sitemaps</link>"
         and some worked examples are shown in the following sections here.
@@ -702,7 +702,7 @@
         and related component documentation.
         The Forrest sitemap is broken into multiple files. The main one is
         <strong>sitemap.xmap</strong> which delegates to others.  See the
-         <link href="site:v0.80//sitemap-ref">Sitemap Reference</link> for a tour of the
+         <link href="site:sitemap-ref">Sitemap Reference</link> for a tour of the
         default sitemap.
       <section id="adding_new_content_type">
@@ -819,7 +819,7 @@
             structure into the Forrest intermediate xdocs structure.
-            The <link href="site:v0.80//sitemap-ref">Sitemap
+            The <link href="site:sitemap-ref">Sitemap
             Reference</link> provides details about how the sitemap works.
@@ -856,7 +856,7 @@
                  By default, Forrest requires that all XML files be valid, i.e.
                  they must have a DOCTYPE declaration and associated DTD, and
                  validate against it.  Our new 'downloads' document type is no
-                 exception.  The <link href="site:v0.80//validation">XML
+                 exception.  The <link href="site:validation">XML
                    Validation</link> document continues this example, showing how
                  to register a new document type.  Briefly, this involves:
@@ -870,7 +870,7 @@
                  <li>Tell the system about your catalog.</li>
-                 Please see <link href="site:v0.80//validation">XML Validation</link>
+                 Please see <link href="site:validation">XML Validation</link>
                  for the complete description for those steps.
@@ -886,7 +886,7 @@
               We need to digress and explain the powerful 
-              <link href="site:v0.80//cap">SourceTypeAction (content aware pipelines)</link>.
+              <link href="site:cap">SourceTypeAction (content aware pipelines)</link>.
               It is a Cocoon sitemap component that peeks at the top-part of
               a document to look for hints about the type of the document.
               It has four methods: document-declaration, document-element and
@@ -947,7 +947,7 @@
               This is the type of processing that happens in the main
               <code>main/webapp/forrest.xmap</code> sitemap. We have
               added similar handling to our project sitemap. Basically, this
-              uses the <link href="site:v0.80//cap">SourceTypeAction (content aware pipelines)</link>
+              uses the <link href="site:cap">SourceTypeAction (content aware pipelines)</link>
               to detect the doctype. The new document-v11.dtd needs to be also
               added to your project Catalog as
               <link href="#new_dtd">described above</link>.
@@ -1008,7 +1008,7 @@
           Forrest supplies a collection of 
-          <link href="site:v0.80//skins">default skins</link> which are configurable
+          <link href="site:skins">default skins</link> which are configurable
           and so should meet the needs of most projects. The aim is to provide
           many capabilities so that extra skins are not needed.
@@ -1094,7 +1094,7 @@
         In comparison to simpler tools (like 
         <link href="ext:anakia">Anakia</link>) the Cocoon command-line mode
         (and hence Forrest command-line mode) is slow.
-        As the <link href="site:v0.80//dreams">dream list</link> notes, Forrest was
+        As the <link href="site:dreams">dream list</link> notes, Forrest was
         originally intended to be used for
         dynamic sites, and the Cocoon crawler used only to create static
         snapshots for mirroring.  This section describes how, by using

Modified: forrest/trunk/site-author/content/xdocs/howto-dev.xml
--- forrest/trunk/site-author/content/xdocs/howto-dev.xml (original)
+++ forrest/trunk/site-author/content/xdocs/howto-dev.xml Sun Mar  4 22:32:17 2007
@@ -69,12 +69,12 @@
         You have achieved the basic level of using Forrest. You have Forrest
         installed and can create a new site with 'forrest seed'.
         You have followed at least the first parts of the 
-        <a href="site:v0.80//your-project">Using Forrest</a>
+        <a href="site:your-project">Using Forrest</a>
         You will enventually see that understanding of the Cocoon
-        <a href="site:v0.80//sitemap-ref">sitemap</a>
+        <a href="site:sitemap-ref">sitemap</a>
         is important. For the initial examples below, you can do without that.
         However please explore the sitemap soon.
@@ -147,7 +147,7 @@
         To get started, see the
-        <a href="site:v0.80//build">instructions</a>
+        <a href="site:build">instructions</a>
         for obtaining the Apache Forrest sources via SVN.
@@ -284,7 +284,7 @@
       <title>Editing content</title>
         See the 
-        <a href="site:v0.80//faq/edit-content">FAQ</a>.
+        <a href="site:faq/edit-content">FAQ</a>.
         Basically any editor can
         be used, because Forrest treats the editing of content as a separate
         concern. Be sure to configure the editor to find local copies of DTDs.
@@ -377,11 +377,11 @@
         The Cocoon sitemap is essential for Forrest developers. See some introductions ....
-        <li><a href="site:v0.80//sitemap-ref">Forrest sitemap reference</a>.</li>
+        <li><a href="site:sitemap-ref">Forrest sitemap reference</a>.</li>
         <li>Introduction to Pipelines in this
-          <a href="site:v0.80//custom-html-source">How-to</a>.</li>
+          <a href="site:custom-html-source">How-to</a>.</li>
-          <a href="site:v0.80//project-sitemap">Forrest project sitemaps</a>.</li>
+          <a href="site:project-sitemap">Forrest project sitemaps</a>.</li>
         <li><a href="ext:cocoon/concepts">Cocoon concepts</a>.</li>
         <li><a href="ext:cocoon/sitemap">Cocoon sitemap</a>.</li>
         <li><a href="ext:cocoon/protocols">Cocoon protocols</a>, i.e. cocoon:/ and
@@ -403,7 +403,7 @@
           the "logkit.xconf" in webapp/WEB-INF and raise the level of some loggers to WARN.
-          This <a href="site:v0.80//faq/logs">FAQ</a>
+          This <a href="site:faq/logs">FAQ</a>
           describes the location of the Cocoon logfiles and their
@@ -547,7 +547,7 @@
           Do 'forrest site' to produce the whole documentation set.
           Cocoon will report its progress and reveal any problems.
-          This <a href="site:v0.80//faq/build_msg_a">FAQ</a>
+          This <a href="site:faq/build_msg_a">FAQ</a>
           explains the messages that Cocoon sends to standard output.
           Broken links are also reported to a special file, which also shows
           the source file containing the break. The location

Modified: forrest/trunk/site-author/content/xdocs/pluginDocs/index.xml
--- forrest/trunk/site-author/content/xdocs/pluginDocs/index.xml (original)
+++ forrest/trunk/site-author/content/xdocs/pluginDocs/index.xml Sun Mar  4 22:32:17 2007
@@ -26,7 +26,7 @@
       <li><a href="site:v0.70/plugins/index">0.7</a> - the current release</li>
-      <li><a href="site:v0.80/plugins/index">0.8-dev</a> - the current development version</li>
+      <li><a href="site:plugins/index">0.8-dev</a> - the current development version</li>

Modified: forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/pluginInfrastructure.xml
--- forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/pluginInfrastructure.xml (original)
+++ forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/pluginInfrastructure.xml Sun Mar  4 22:32:17 2007
@@ -295,7 +295,7 @@
 		<title>Further Reading</title>
 		<p>If you want to build a plugin you might like to start with our 
-		<a href="site:v0.80//buildPlugin">HowTo on Building Plugins</a>.</p>
+		<a href="site:buildPlugin">HowTo on Building Plugins</a>.</p>

Modified: forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/usingPlugins.xml
--- forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/usingPlugins.xml (original)
+++ forrest/trunk/site-author/content/xdocs/pluginDocs/plugins_0_80/usingPlugins.xml Sun Mar  4 22:32:17 2007
@@ -217,7 +217,7 @@
       <title>Further Reading</title>
         <li><a href="site:plugins/infrastructure">Plugin Infrastructure</a></li>
-        <li><a href="site:v0.80//buildPlugin">How to build a Plugin</a></li>
+        <li><a href="site:buildPlugin">How to build a Plugin</a></li>

Modified: forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
--- forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml (original)
+++ forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml Sun Mar  4 22:32:17 2007
@@ -261,7 +261,7 @@
  <versions tab="docs">
     <overview label="Overview" href="versions/index.html"/>
-    <v0.8 label="0.8-dev" href="site:v0.80//index"/>
+    <v0.8 label="0.8-dev" href="site:index"/>
     <v0.7 label="0.7 (current)" href="site:v0.70//index"/>
     <v0.6 label="0.6" href="site:v0.60//index"/>
@@ -272,7 +272,7 @@
  <versions tab="docs">
     <overview label="Overview" href="versions/index.html"/>
-    <v0.9 label="0.9-dev" href="site:v0.90//index"/>
+    <v0.9 label="0.9-dev" href="site:index"/>
     <v0.8 label="0.8 (current)" href="site:v0.80//index"/>
     <v0.7 label="0.7" href="site:v0.70//index"/>
@@ -285,19 +285,6 @@
                     <p>Remove the past versions (0.6) docs directory by doing 'svn rm site-author/content/xdocs/docs_0_60</p>
                     <fixme author="">Do we also remove the generated docs from forrest/site/docs_0_60 SVN? This also removes it from the website.</fixme>
-                </li>
-                <li>
-                    <p>Adjust version-numbers in site.xml</p>
-                    <fixme author="fso">This used to be the comment: 'Do global replace throughout docs_0_80 to replace the string
-                        ="site:v0.70 with ="site:v0.80' but this needs checking.</fixme>
-                    <fixme author="dc">Perhaps you are talking about something else.
-                      I meant that when we copy the docs to become the next -dev (i.e.
-                      this time docs_0_90) then we need to replace all "site:" references
-                      (i.e. ="site:v0.80 with ="site:v0.90'). If you can see a better way, then great.
-                     Maybe dropping the v0.x prefix will cause it to use the most recent doc,
-                     e.g. use site:buildPlugin rather than site:v0.90/howto/buildplugin.
-                  </fixme>

Modified: forrest/trunk/site-author/content/xdocs/site.xml
--- forrest/trunk/site-author/content/xdocs/site.xml (original)
+++ forrest/trunk/site-author/content/xdocs/site.xml Sun Mar  4 22:32:17 2007
@@ -221,14 +221,14 @@
   <versions tab="docs">
     <overview label="Overview" href="versions/index.html"/>
-    <v0.8 label="0.8-dev" href="site:v0.80//index"/>
+    <v0.8 label="0.8-dev" href="site:index"/>
     <v0.7 label="0.7 (current)" href="site:v0.70//index"/>
     <v0.6 label="0.6" href="site:v0.60//index"/>
   <pluginVersions tab="plugins">
     <overview label="Overview" href="pluginDocs/index.html"/>
-    <v0.8 label="0.8-dev" href="site:v0.80//plugins/index"/>
+    <v0.8 label="0.8-dev" href="site:plugins/index"/>
     <v0.7 label="0.7 (current)" href="site:v0.70//plugins/index"/>

Modified: forrest/trunk/site-author/content/xdocs/versions/index.xml
--- forrest/trunk/site-author/content/xdocs/versions/index.xml (original)
+++ forrest/trunk/site-author/content/xdocs/versions/index.xml Sun Mar  4 22:32:17 2007
@@ -27,7 +27,7 @@
       <li><a href="site:v0.60/documentation/index">0.6</a> - the past release</li>
       <li><a href="site:v0.70/documentation/index">0.7</a> - the current release</li>
-      <li><a href="site:v0.80/documentation/index">0.8-dev</a> - the current development version</li>
+      <li><a href="site:documentation/index">0.8-dev</a> - the current development version</li>

Modified: forrest/trunk/site-author/content/xdocs/who.xml
--- forrest/trunk/site-author/content/xdocs/who.xml (original)
+++ forrest/trunk/site-author/content/xdocs/who.xml Sun Mar  4 22:32:17 2007
@@ -31,7 +31,7 @@
         Of course the committers are not the only people involved in the community.
         Thanks to the many people for their contributions
         of patches, assistance, ideas, and email discussion.
-        Some are mentioned at the <a href="site:v0.80//changes">changes</a> page.
+        Some are mentioned at the <a href="site:changes">changes</a> page.
         See how we <a href="guidelines.html#contribution">acknowledge</a> contributions.

View raw message