forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From je...@apache.org
Subject cvs commit: xml-forrest/src/documentation/content/xdocs/community/howto/xmlform howto-xmlform.xml step1.xml step2.xml step3.xml step4.xml step5.xml book.xml
Date Sun, 05 Jan 2003 16:17:08 GMT
jefft       2003/01/05 08:17:07

  Modified:    src/documentation/content/xdocs Tag: LINKMAP_BRANCH
                        contrib.xml dreams.xml faq.xml forrest-contract.xml
                        forrestbot-intro.xml forrestbot.xml libre-intro.xml
                        mail-lists.xml primer.xml your-project.xml
               src/documentation/content/xdocs/community/howto Tag:
                        LINKMAP_BRANCH index.xml
               src/documentation/content/xdocs/community/howto/bugzilla-patch
                        Tag: LINKMAP_BRANCH howto-bugzilla-patch.xml
               src/documentation/content/xdocs/community/howto/xmlform Tag:
                        LINKMAP_BRANCH howto-xmlform.xml step1.xml
                        step2.xml step3.xml step4.xml step5.xml
  Removed:     src/documentation/content/xdocs Tag: LINKMAP_BRANCH
                        howto-v10.xml
               src/documentation/content/xdocs/community/howto/cvs-ssh Tag:
                        LINKMAP_BRANCH book.xml
               src/documentation/content/xdocs/community/howto/v10 Tag:
                        LINKMAP_BRANCH book.xml
               src/documentation/content/xdocs/community/howto/xmlform Tag:
                        LINKMAP_BRANCH book.xml
  Log:
  - Convert most remaining *.html links to site: links
  - Remove some more book.xml in favour of site.xml-generated menus
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.6.4.1   +3 -3      xml-forrest/src/documentation/content/xdocs/contrib.xml
  
  Index: contrib.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/contrib.xml,v
  retrieving revision 1.6
  retrieving revision 1.6.4.1
  diff -u -r1.6 -r1.6.4.1
  --- contrib.xml	6 Jun 2002 14:32:39 -0000	1.6
  +++ contrib.xml	5 Jan 2003 16:17:06 -0000	1.6.4.1
  @@ -17,7 +17,7 @@
         resource donations (money, time, publicity, hardware, software, conference
         presentations, speeches, etc...). </p>
         <p> To begin with, we suggest you to subscribe to the
  -        <link href="mail-lists.html">Forrest mailing lists</link> (follow the
link for
  +        <link href="site:mail-lists">Forrest mailing lists</link> (follow the
link for
         information on how to subscribe and to access the mail list archives).
         Listen-in for a while, to hear how others make contributions. </p>
         <p>You can get your local working copy of the
  @@ -49,7 +49,7 @@
         <li>Specifying/analysing/designing new features - and beyond. (If you
           wish to get involved with this, please join <code>general Forrest mailing
           list</code>, install and try out Forrest and read some of the
  -        <link href="mail-lists.html">mail archives</link>. You should have
a strong
  +        <link href="site:mail-lists">mail archives</link>. You should have
a strong
         "fluency" in XML technologies, Java and a basic understanding of the Forrest
         architecture - don't just say "it should have XYZ" without reading anything
         first - because chances are, somebodies already thought of that feature!)</li>
  @@ -101,7 +101,7 @@
           patches. So that everyone can be productive, it is important to know which
           method is appropriate for a certain situation and how to go about it without
           confusion. This section explains when to use the <code>developer</code>
  -        <link href="mail-lists.html">mailing list</link> the bug database.
</p>
  +        <link href="site:mail-lists">mailing list</link> the bug database.
</p>
         <p> Research your topic thoroughly before beginning to discuss a new
           development issue. Search and browse through the email archives - your issue
           may have been discussed before. Prepare your post clearly and concisely. </p>
  
  
  
  1.7.4.1   +1 -1      xml-forrest/src/documentation/content/xdocs/dreams.xml
  
  Index: dreams.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/dreams.xml,v
  retrieving revision 1.7
  retrieving revision 1.7.4.1
  diff -u -r1.7 -r1.7.4.1
  --- dreams.xml	30 Jul 2002 03:41:46 -0000	1.7
  +++ dreams.xml	5 Jan 2003 16:17:06 -0000	1.7.4.1
  @@ -19,7 +19,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="primer.html">Forrest Primer</link>
  +   focus document. The <link href="site:primer">Forrest Primer</link>
      provides an overview.
     </p>
   
  
  
  
  1.16.4.1  +8 -10     xml-forrest/src/documentation/content/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/faq.xml,v
  retrieving revision 1.16
  retrieving revision 1.16.4.1
  diff -u -r1.16 -r1.16.4.1
  --- faq.xml	14 Nov 2002 08:54:37 -0000	1.16
  +++ faq.xml	5 Jan 2003 16:17:06 -0000	1.16.4.1
  @@ -11,8 +11,8 @@
     <p>
      Because we are in transition to the new document-v11.dtd
      and there are still some stylesheets that need tweaking.
  -   See the <link href="document-v11.html">Demo document-v11</link>
  -   and <link href="compliance.html">Standards Compliance</link>.
  +   See the <link href="site:samples/document-v11">Demo document-v11</link>
  +   and <link href="site:compliance">Standards Compliance</link>.
     </p>
    </answer>
   </faq>
  @@ -46,10 +46,8 @@
      then copy the basic skin to make your own.
     </p>
     <p>
  -   The <link href="forrestbot.html">forrestbot</link> is under-development
to
  +   The <link href="site:forrestbot">forrestbot</link> is under-development
to
      automate the production of your documentation.
  -   Set it up for your own projects by following this
  -   <link href="forrestbot-intro.html">concise overview</link>. 
     </p>
    </answer>
   </faq>
  @@ -63,7 +61,7 @@
      Sorry, we are working on that for the next release. Forrest development has
      been very fast recently. Some of the documentation refers to old methods.
      Your best bet is to start with the
  -   <link href="your-project.html">Using Forrest</link> document.
  +   <link href="site:your-project">Using Forrest</link> document.
     </p>
    </answer>
   </faq>
  @@ -74,11 +72,11 @@
    </question>
    <answer>
     <p>
  -   Join the forrest-dev <link href="mail-lists.html">mailing list</link>
  +    Join the forrest-dev <link href="site:mail-lists">mailing list</link>
      and help to discuss it. Read the 
  -   <link href="primer.html">Forrest Primer</link> for an overview.
  +   <link href="site:primer">Forrest Primer</link> for an overview.
      See the 
  -   <link href="todo.html">To Do List </link> and choose something that
  +   <link href="site:todo">To Do List </link> and choose something that
      interests you.
     </p>
    </answer>
  @@ -91,7 +89,7 @@
    <answer>
     <p>
      It is a bug. Workaround: <code>./build.sh clean docs</code> every time.
  -   There is an entry on the <link href="todo.html">To Do List</link>.
  +   There is an entry on the <link href="site:todo">To Do List</link>.
     </p>
    </answer>
   </faq>
  
  
  
  1.5.2.1   +2 -2      xml-forrest/src/documentation/content/xdocs/forrest-contract.xml
  
  Index: forrest-contract.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/forrest-contract.xml,v
  retrieving revision 1.5
  retrieving revision 1.5.2.1
  diff -u -r1.5 -r1.5.2.1
  --- forrest-contract.xml	24 Dec 2002 02:04:22 -0000	1.5
  +++ forrest-contract.xml	5 Jan 2003 16:17:06 -0000	1.5.2.1
  @@ -8,7 +8,7 @@
         contract is described in the implementation details of the full distribution.
         This tries to list (not explain) what the ins and outs of using Forrest is
         about. Please let the forrest-dev
  -      <link href="mail-lists.html">mail list</link> know if
  +      <link href="site:mail-lists">mail list</link> know if
         any of the bullets listed here are out of sync with the real
         implementation.</notice>
       <abstract>This document describes in a very techy bullet-style way how to use
Forrest.</abstract> 
  @@ -22,7 +22,7 @@
         <ul> 
           <li>provide DTDs, skins, cocoon-pipelines, and a willing team of
             supporting developers at the forrest-dev
  -          <link href="mail-lists.html">mail list</link></li>
  +          <link href="site:mail-lists">mail list</link></li>
         <li>use Cocoon to generate the HTML documentation for TheProject</li>

         </ul> 
       </section> 
  
  
  
  1.2.4.1   +3 -3      xml-forrest/src/documentation/content/xdocs/forrestbot-intro.xml
  
  Index: forrestbot-intro.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/forrestbot-intro.xml,v
  retrieving revision 1.2
  retrieving revision 1.2.4.1
  diff -u -r1.2 -r1.2.4.1
  --- forrestbot-intro.xml	14 Nov 2002 09:00:54 -0000	1.2
  +++ forrestbot-intro.xml	5 Jan 2003 16:17:06 -0000	1.2.4.1
  @@ -35,8 +35,8 @@
     </p>
     <p>
      This document provides a concise overview of one particular scenario. See
  -   <link href="forrestbot.html">The ForrestBot</link> for details and understand
  -   <link href="forrest-contract.html">Our Contract</link>.
  +   <link href="site:forrestbot">The ForrestBot</link> for details and understand
  +   <link href="site:forrest-contract">Our Contract</link>.
      Please send your feedback to <code>forrest-dev</code> - the ForrestBot
      will be enhanced to meet diverse needs.
     </p>
  @@ -115,7 +115,7 @@
   
    <section>
     <title>Other methods</title>
  -  <p>See the <link href="your-project.html">Using Forrest</link> document.</p>
  +  <p>See the <link href="site:your-project">Using Forrest</link> document.</p>
     <p>Forrest can also run as a dynamic webapp.</p>
    </section>
   
  
  
  
  1.4.2.1   +5 -5      xml-forrest/src/documentation/content/xdocs/forrestbot.xml
  
  Index: forrestbot.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/forrestbot.xml,v
  retrieving revision 1.4
  retrieving revision 1.4.2.1
  diff -u -r1.4 -r1.4.2.1
  --- forrestbot.xml	24 Dec 2002 02:04:22 -0000	1.4
  +++ forrestbot.xml	5 Jan 2003 16:17:06 -0000	1.4.2.1
  @@ -18,10 +18,10 @@
         functionality, and how they could be extended in the future.</p> 
       <p>See some related documents:</p>
       <ul>
  -     <li><link href="forrest-contract.html">Our Contract</link>
  +     <li><link href="site:forrest-contract">Our Contract</link>
         - explains the rules with which your project should comply
        </li>
  -     <li><link href="your-project.html">Your Project</link>
  +     <li><link href="site:your-project">Your Project</link>
         - getting started with using Forrest (concise overview of forrestbot)
        </li>
       </ul>
  @@ -212,7 +212,7 @@
         <note>Once you understand all of this you might decide NOT to run your
           own centralized service but rather ask your project to be taken up in the
           centralized service of the project team itself: just send a mail to
  -        forrest-dev <link href="mail-lists.html">mail list</link>
  +        forrest-dev <link href="site:mail-lists">mail list</link>
           defining the required parameters to be taken up in the
           process.</note> 
         <section> 
  @@ -226,11 +226,11 @@
             all workstages have been completed (or as soon as building failed)</p>

         </section> 
       </section> 
  -    <section><title>Current supported workstages and types.</title><section><title><code>&lt;prepare&gt;</code></title><p>No
specific type versions. (don't use type-attribute)</p><p>Template arguments:</p><ul><li><code>&lt;skin&gt;</code>
@name holds the name of the skin to use.</li></ul></section><section><title><code>&lt;get-src
...&gt;</code></title><section><title><code>&lt;get-src
type="cvs"&gt;</code></title><p>Template arguments:</p><ul><li><code>&lt;host&gt;</code>
@name holds the ipaddress or dns name of the  cvs serving host</li><li><code>&lt;root&gt;</code>
@name holds the cvs-root directory on that host</li><li><code>&lt;user&gt;</code>
@name holds the username to use on the cvs repository </li><li><code>&lt;passwd&gt;</code>
@name holds the password to use on the cvs repository</li><li><code>&lt;module&gt;</code>
@name holds the module name that holds the </li><li><code>&lt;dir&gt;</code>
@name holds the relative path to the {docroot} directory.  (This is the dir  that is holding
the ./content/xdocs as specified in t. </li></ul></section><section><title><code>&lt;get-src
type="local-copy"&gt;</code></title><p>Template arguments:</p><ul><li><code>&lt;content-dir/&gt;</code>
@name holds the path pointing to the {docroot} directory. (See the <link href="forrest-contract.html">contract</link>
to understand what should be there.)</li><li><code>&lt;project-dir/&gt;</code>
@name holds the path pointing to the {projecthome} directory where the xml project descriptors
reside.</li></ul></section></section><section><title><code>&lt;generate&gt;</code></title><p>No
specific type versions. (don't use type-attribute)</p><p>Template arguments:</p><ul><li><code>&lt;debuglevel&gt;</code>
@name holds the threshold-level for showing debug statements in the cocoon generation process.</li></ul></section><section><title><code>&lt;deploy
...&gt;</code></title><section><title><code>&lt;deploy
type="scp"&gt;</code></title><p>Template arguments:</p><ul><li><code>&lt;host&gt;</code>
@name holds the remote host where the file will be copied to.</li><li><code>&lt;user&gt;</code>
@name holds the username to be used when logging onto the remote host.</li><li><code>&lt;root&gt;</code>
@name holds the prefix part of where the content needs to be published.</li><li><code>&lt;dir&gt;</code>
@name holds the suffix part of where the content needs to be published.</li></ul><warning>Using
this approach requires that the public key of the user executing the bot target is present
in the authorized key file (<code>~/.ssh/authorized_keys2</code>) of the remote
user (on the remote host).</warning><note>Might be interesting to understand that
the full process actually is bundling all files to copy in a *.tar.gz that is un-tar.gzipped
on the remote host using ssh. </note></section><section><title><code>&lt;deploy
type="local-copy"&gt;</code></title><p>Template arguments:</p><ul><li><code>&lt;destination&gt;</code>
@name holds the path where the generated content needs to be copied to.</li></ul></section><section><title><code>&lt;deploy
type="ftp"&gt;</code></title><p>Template arguments:</p><ul><li><code>&lt;host&gt;</code>
@name holds the hostname of the ftp server to publish to.</li><li><code>&lt;user&gt;</code>
@name holds the username to use for loging onto the ftp server.</li><li><code>&lt;passwd&gt;</code>
@name holds the password to use.</li><li><code>&lt;destination&gt;</code>
@name holds the path to the directory on the remote host where the generated content needs
to be published.  The process is using the <code>ftp cd</code> command to get
there.  This means this directory has to exist.</li></ul></section><warning>Currently
the ant distribution that is included in forrest cvs is not offering the required NetComponents.jar
to actually support this type of deployment. If you want to use it anyway you should use get
the required jar from <link href="http://www.savarese.org/oro/downloads/index.html#NetComponents">http://www.savarese.org/oro/downloads</link>
and drop that into your <code>{forrest-sandbox}/tools/antipede/lib</code> directory.
 </warning></section><section><title><code>&lt;cleanup&gt;</code></title><p>No
specific type versions. (don't use type-attribute)</p><p>Template arguments: None.</p></section></section><section>

  +    <section><title>Current supported workstages and types.</title><section><title><code>&lt;prepare&gt;</code></title><p>No
specific type versions. (don't use type-attribute)</p><p>Template arguments:</p><ul><li><code>&lt;skin&gt;</code>
@name holds the name of the skin to use.</li></ul></section><section><title><code>&lt;get-src
...&gt;</code></title><section><title><code>&lt;get-src
type="cvs"&gt;</code></title><p>Template arguments:</p><ul><li><code>&lt;host&gt;</code>
@name holds the ipaddress or dns name of the  cvs serving host</li><li><code>&lt;root&gt;</code>
@name holds the cvs-root directory on that host</li><li><code>&lt;user&gt;</code>
@name holds the username to use on the cvs repository </li><li><code>&lt;passwd&gt;</code>
@name holds the password to use on the cvs repository</li><li><code>&lt;module&gt;</code>
@name holds the module name that holds the </li><li><code>&lt;dir&gt;</code>
@name holds the relative path to the {docroot} directory.  (This is the dir  that is holding
the ./content/xdocs as specified in t. </li></ul></section><section><title><code>&lt;get-src
type="local-copy"&gt;</code></title><p>Template arguments:</p><ul><li><code>&lt;content-dir/&gt;</code>
@name holds the path pointing to the {docroot} directory. (See the <link href="site:forrest-contract">contract</link>
to understand what should be there.)</li><li><code>&lt;project-dir/&gt;</code>
@name holds the path pointing to the {projecthome} directory where the xml project descriptors
reside.</li></ul></section></section><section><title><code>&lt;generate&gt;</code></title><p>No
specific type versions. (don't use type-attribute)</p><p>Template arguments:</p><ul><li><code>&lt;debuglevel&gt;</code>
@name holds the threshold-level for showing debug statements in the cocoon generation process.</li></ul></section><section><title><code>&lt;deploy
...&gt;</code></title><section><title><code>&lt;deploy
type="scp"&gt;</code></title><p>Template arguments:</p><ul><li><code>&lt;host&gt;</code>
@name holds the remote host where the file will be copied to.</li><li><code>&lt;user&gt;</code>
@name holds the username to be used when logging onto the remote host.</li><li><code>&lt;root&gt;</code>
@name holds the prefix part of where the content needs to be published.</li><li><code>&lt;dir&gt;</code>
@name holds the suffix part of where the content needs to be published.</li></ul><warning>Using
this approach requires that the public key of the user executing the bot target is present
in the authorized key file (<code>~/.ssh/authorized_keys2</code>) of the remote
user (on the remote host).</warning><note>Might be interesting to understand that
the full process actually is bundling all files to copy in a *.tar.gz that is un-tar.gzipped
on the remote host using ssh. </note></section><section><title><code>&lt;deploy
type="local-copy"&gt;</code></title><p>Template arguments:</p><ul><li><code>&lt;destination&gt;</code>
@name holds the path where the generated content needs to be copied to.</li></ul></section><section><title><code>&lt;deploy
type="ftp"&gt;</code></title><p>Template arguments:</p><ul><li><code>&lt;host&gt;</code>
@name holds the hostname of the ftp server to publish to.</li><li><code>&lt;user&gt;</code>
@name holds the username to use for loging onto the ftp server.</li><li><code>&lt;passwd&gt;</code>
@name holds the password to use.</li><li><code>&lt;destination&gt;</code>
@name holds the path to the directory on the remote host where the generated content needs
to be published.  The process is using the <code>ftp cd</code> command to get
there.  This means this directory has to exist.</li></ul></section><warning>Currently
the ant distribution that is included in forrest cvs is not offering the required NetComponents.jar
to actually support this type of deployment. If you want to use it anyway you should use get
the required jar from <link href="http://www.savarese.org/oro/downloads/index.html#NetComponents">http://www.savarese.org/oro/downloads</link>
and drop that into your <code>{forrest-sandbox}/tools/antipede/lib</code> directory.
 </warning></section><section><title><code>&lt;cleanup&gt;</code></title><p>No
specific type versions. (don't use type-attribute)</p><p>Template arguments: None.</p></section></section><section>

         <title>ForrestBot design</title> 
         <p>Most of us will just like things to work, and will be happy enough
           just using it, maybe even letting the forrest-dev
  -        <link href="mail-lists.html">mail list</link> know if we could improve
  +        <link href="site:mail-lists">mail list</link> know if we could improve
           this or the other. Some however might be drawn to the
         <link href="http://www.howstuffworks.com/">how stuff works</link> of
things.
         For them is this section as a start in the rest of their own pursuit.</p> 
  
  
  
  1.4.2.1   +1 -1      xml-forrest/src/documentation/content/xdocs/libre-intro.xml
  
  Index: libre-intro.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/libre-intro.xml,v
  retrieving revision 1.4
  retrieving revision 1.4.2.1
  diff -u -r1.4 -r1.4.2.1
  --- libre-intro.xml	24 Dec 2002 02:04:22 -0000	1.4
  +++ libre-intro.xml	5 Jan 2003 16:17:06 -0000	1.4.2.1
  @@ -357,7 +357,7 @@
       <section> 
         <title>Next Libre (0.1)</title> 
         <note>Next libre is in fact largely in your hands... just drop
  -        the forrest-dev <link href="mail-lists.html">mail list</link>
  +        the forrest-dev <link href="site:mail-lists">mail list</link>
           a line, and see what happens...</note> 
         <section> 
           <title>Itches</title> 
  
  
  
  1.6.4.1   +3 -3      xml-forrest/src/documentation/content/xdocs/mail-lists.xml
  
  Index: mail-lists.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/mail-lists.xml,v
  retrieving revision 1.6
  retrieving revision 1.6.4.1
  diff -u -r1.6 -r1.6.4.1
  --- mail-lists.xml	14 Nov 2002 09:04:10 -0000	1.6
  +++ mail-lists.xml	5 Jan 2003 16:17:06 -0000	1.6.4.1
  @@ -13,12 +13,12 @@
         <p><strong>IMPORTANT: Before posting a question or problem to any mailing
           list, </strong>please first look at the following resources:</p> 
   <ul> 
  -<li><link href="faq.html">Forrest FAQs</link></li> 
  -<li><link href="index.html">Forrest documentation</link></li> 
  +<li><link href="site:faq">Forrest FAQs</link></li> 
  +<li><link href="site:index">Forrest documentation</link></li> 
   <li><link href="http://xml.apache.org/cocoon/link/">Cocoon Links</link>
   for pointers to general XML and XSL and Java related resources.
   Please do not ask such questions here unless they are related to Forrest.</li> 
  -<li><link href="mail-archives.html">Mailing list archives</link> - a
  +<li><link href="site:mail-archives">Mailing list archives</link> - a
   veritable goldmine of Forrest-specific information.</li> 
   </ul> 
         <p><strong>IMPORTANT:</strong> If you are posting about a problem
that
  
  
  
  1.18.2.1  +5 -5      xml-forrest/src/documentation/content/xdocs/primer.xml
  
  Index: primer.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/primer.xml,v
  retrieving revision 1.18
  retrieving revision 1.18.2.1
  diff -u -r1.18 -r1.18.2.1
  --- primer.xml	24 Dec 2002 02:04:22 -0000	1.18
  +++ primer.xml	5 Jan 2003 16:17:06 -0000	1.18.2.1
  @@ -19,7 +19,7 @@
         actual progress of the Forrest project. As such, the primer will be enhanced,
         restructured and edited to provide an accessible entry point for new
         Forresteers. Please send all comments, patches and suggestions to
  -      the forrest-dev <link href="mail-lists.html">mail list</link>.</note>

  +      the forrest-dev <link href="site:mail-lists">mail list</link>.</note>

       <section>
         <title>History</title> 
         <p>Forrest has come into existence because of the abysmal state of the
  @@ -40,7 +40,7 @@
         <p>The Forrest vision was articulated by Stefano Mazzocchi and Sam Ruby,
           both long-time contributors to Apache projects, in the beginning of 2002, and
           was rapidly picked up by a bunch of other <link
  -          href="who.html">contributors</link> as well, after a headstart by Nicola
Ken
  +          href="site:who">contributors</link> as well, after a headstart by Nicola
Ken
           Barozzi. So here we are, plenty of work-in-progress to erect what eventually
           will become a true community website infrastructure for Apache open source
           development.</p> 
  @@ -115,7 +115,7 @@
             valuable and in true community spirit, you can possibly gain commit access to
             the Forrest CVS repository and become an Apache committer. The first stage
             towards becoming a contributor is to join the forrest dev
  -          <link href="mail-lists.html">mailing list</link>, the second is to
download
  +          <link href="site:mail-lists">mailing list</link>, the second is to
download
             Forrest and start playing with it (see below).</li> 
         </ul> 
         <p>Depending on your role, your potential area of interest in Forrest
  @@ -419,7 +419,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="dreams.html">dream list</link> that lists most of them.</p>

  +        <link href="site:dreams">dream list</link> that lists most of them.</p>

         <ul> 
           <li>Our first ambition is to support the project site generation and
             maintenance of other Apache projects in an automated manner, starting with our
  @@ -519,7 +519,7 @@
           <li>Unix shell scripting / CVS / cron gurus, preferably bearded</li>

         </ul> 
         <p>Just drop us a line at 
  -       the forrest-dev <link href="mail-lists.html">mail list</link>.
  +       the forrest-dev <link href="site:mail-lists">mail list</link>.
         </p>
   
       </section> 
  
  
  
  1.18.2.1  +6 -6      xml-forrest/src/documentation/content/xdocs/your-project.xml
  
  Index: your-project.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/your-project.xml,v
  retrieving revision 1.18
  retrieving revision 1.18.2.1
  diff -u -r1.18 -r1.18.2.1
  --- your-project.xml	24 Dec 2002 02:04:22 -0000	1.18
  +++ your-project.xml	5 Jan 2003 16:17:07 -0000	1.18.2.1
  @@ -398,7 +398,7 @@
             Forrest's own xdocs for an example.</p>
           <note>Yes, we know it is a pain having to edit every directory's
             <code>book.xml</code>
  -          file when making changes. The <link href="libre-intro.html">Libre</link>
  +          file when making changes. The <link href="site:libre-intro">Libre</link>
             effort will hopefully put an end to this</note>
         </section>
         <section>
  @@ -615,7 +615,7 @@
                    By default, Forrest requires that all XML files be valid: ie
                    they must have a DOCTYPE declaration and associated DTD, and
                    validate against it.  Our new 'downloads' document type is no
  -                 exception.  The <link href="validation.html">XML
  +                 exception.  The <link href="site:validation">XML
                      Validation</link> section continues this example, showing how
                    to register a new document type.  Briefly, this involves:
                  </p>
  @@ -631,7 +631,7 @@
                        "dtd/download-v11.dtd"</code></li>
                  </ul>
                  <p>
  -                 Please read <link href="validation.html">XML Validation</link>
  +                 Please read <link href="site:validation">XML Validation</link>
                    for the full story.
                  </p>
               </section>
  @@ -796,7 +796,7 @@
             In comparison to simpler tools like <link
               href="http://jakarta.apache.org/velocity/anakia.html">Anakia</link>,
             Cocoon's command-line mode (and hence Forrest) is painfully slow.  As the
  -          <link href="dreams.html">dream list</link> notes, Forrest was originally
  +          <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
             developing with a "live" Forrest webapp instance, Forrest-based doc
  @@ -870,7 +870,7 @@
               into the <code>build/</code> directory.  There are also suggestions
for making
               webapp-based content generation the primary technique. Future
               directions like these are debated on 
  -            the forrest-dev <link href="mail-lists.html">mail list</link>.
  +            the forrest-dev <link href="site:mail-lists">mail list</link>.
               Please join if you have any suggestions.
             </note>
           </section>
  
  
  
  No                   revision
  
  
  No                   revision
  
  
  1.4.4.1   +5 -5      xml-forrest/src/documentation/content/xdocs/community/howto/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/index.xml,v
  retrieving revision 1.4
  retrieving revision 1.4.4.1
  diff -u -r1.4 -r1.4.4.1
  --- index.xml	6 Jun 2002 14:32:40 -0000	1.4
  +++ index.xml	5 Jan 2003 16:17:07 -0000	1.4.4.1
  @@ -39,10 +39,10 @@
   on the howto-v10 DTD and stylesheets. Please help to correct any deficiency.
   </p>
         <ul>
  -<li><link href="v10/howto-v10.html">Single Page How-To</link></li>
  -<li><link href="xmlform/howto-xmlform.html">Multi-Page How-To with Revisions</link></li>
  -<li><link href="bugzilla-patch/howto-bugzilla-patch.html">How-To with Images</link></li>
  -  </ul>
  +        <li><link href="site:howto-samples/single-page">Single Page How-To</link></li>
  +        <li><link href="site:howto-samples/xmlform/intro">Multi-Page How-To
with Revisions</link></li>
  +        <li><link href="site:howto-samples/with-images">How-To with Images</link></li>
  +      </ul>
     </section>
   
       <section>
  @@ -53,7 +53,7 @@
   grow and the samples will go away.
   </p>
           <ul>
  -<li><link href="cvs-ssh/howto-cvs-ssh.html">CVS through SSH</link></li>
  +          <li><link href="site:howto-committers/cvs-ssh">CVS through SSH</link></li>
     </ul>
   
     </section>
  
  
  
  No                   revision
  
  
  No                   revision
  
  
  1.4.4.1   +0 -2      xml-forrest/src/documentation/content/xdocs/community/howto/bugzilla-patch/howto-bugzilla-patch.xml
  
  Index: howto-bugzilla-patch.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/bugzilla-patch/howto-bugzilla-patch.xml,v
  retrieving revision 1.4
  retrieving revision 1.4.4.1
  diff -u -r1.4 -r1.4.4.1
  --- howto-bugzilla-patch.xml	6 Jun 2002 14:32:40 -0000	1.4
  +++ howto-bugzilla-patch.xml	5 Jan 2003 16:17:07 -0000	1.4.4.1
  @@ -41,8 +41,6 @@
   </p>
   <ul>
   <li>Understand what a Patch is and how to make one.
  -<!-- See <link href="howto-patch.html">How to Prepare a Patch</link>
  -     Cocoon Doc under development -->
   Note that a new complete document is still just a &quot;patch&quot;,
   though it does need separate treatment to a normal &quot;diff&quot;.
   </li>
  
  
  
  No                   revision
  
  
  No                   revision
  
  
  1.1.4.1   +5 -5      xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/howto-xmlform.xml
  
  Index: howto-xmlform.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/howto-xmlform.xml,v
  retrieving revision 1.1
  retrieving revision 1.1.4.1
  diff -u -r1.1 -r1.1.4.1
  --- howto-xmlform.xml	25 May 2002 07:29:52 -0000	1.1
  +++ howto-xmlform.xml	5 Jan 2003 16:17:07 -0000	1.1.4.1
  @@ -45,11 +45,11 @@
       <steps title="Five Steps">
        <p>Now you want to know how to create your own forms using the Wizard.  Below
are the steps you can follow:</p>
        <ul>
  -       <li><link href="step1.html">Step 1: XML forms</link></li>
  -       <li><link href="step2.html">Step 2: Validation</link></li>
  -       <li><link href="step3.html">Step 3: JavaBean</link></li>
  -       <li><link href="step4.html">Step 4: HowtoWizardAction.java</link></li>
  -       <li><link href="step5.html">Step 5: Sitemap</link></li>
  +       <li><link href="site:xmlform/step1">Step 1: XML forms</link></li>
  +       <li><link href="site:xmlform/step2">Step 2: Validation</link></li>
  +       <li><link href="site:xmlform/step3">Step 3: JavaBean</link></li>
  +       <li><link href="site:xmlform/step4">Step 4: HowtoWizardAction.java</link></li>
  +       <li><link href="site:xmlform/step5">Step 5: Sitemap</link></li>
        </ul>
       </steps>
       
  
  
  
  1.2.4.1   +1 -1      xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step1.xml
  
  Index: step1.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step1.xml,v
  retrieving revision 1.2
  retrieving revision 1.2.4.1
  diff -u -r1.2 -r1.2.4.1
  --- step1.xml	6 Jun 2002 14:32:40 -0000	1.2
  +++ step1.xml	5 Jan 2003 16:17:07 -0000	1.2.4.1
  @@ -509,7 +509,7 @@
            ]]>
           </source>
     </section>
  -        <p><link href="step2.html">Step 2: Validation</link></p>
  +  <p><link href="site:xmlform/step2">Step 2: Validation</link></p>
           
   
       </steps>
  
  
  
  1.2.4.1   +1 -1      xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step2.xml
  
  Index: step2.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step2.xml,v
  retrieving revision 1.2
  retrieving revision 1.2.4.1
  diff -u -r1.2 -r1.2.4.1
  --- step2.xml	6 Jun 2002 14:32:40 -0000	1.2
  +++ step2.xml	5 Jan 2003 16:17:07 -0000	1.2.4.1
  @@ -81,7 +81,7 @@
   </schema>
   ]]>
         </source>  
  -      <p>Now you are ready for <link href="step3.html">Step 3: Java Bean</link>
</p>     
  +      <p>Now you are ready for <link href="site:xmlform/step3">Step 3: Java
Bean</link> </p>     
       </steps>
   
   </howto>
  
  
  
  1.2.4.1   +1 -1      xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step3.xml
  
  Index: step3.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step3.xml,v
  retrieving revision 1.2
  retrieving revision 1.2.4.1
  diff -u -r1.2 -r1.2.4.1
  --- step3.xml	6 Jun 2002 14:32:40 -0000	1.2
  +++ step3.xml	5 Jan 2003 16:17:07 -0000	1.2.4.1
  @@ -210,7 +210,7 @@
   }
   ]]>
           </source>  
  -        <p>Now we move on to <link href="step4.html">Step 4:HowtoWizardAction.java</link></p>
  +        <p>Now we move on to <link href="site:xmlform/step4">Step 4:HowtoWizardAction.java</link></p>
         
         
         </section>
  
  
  
  1.2.4.1   +3 -3      xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step4.xml
  
  Index: step4.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step4.xml,v
  retrieving revision 1.2
  retrieving revision 1.2.4.1
  diff -u -r1.2 -r1.2.4.1
  --- step4.xml	6 Jun 2002 14:32:40 -0000	1.2
  +++ step4.xml	5 Jan 2003 16:17:07 -0000	1.2.4.1
  @@ -746,7 +746,7 @@
   
       ]]>
       </source>
  -    <p>Finally <link href="step5.html">Step 5: the Sitemap</link></p>
  +    <p>Finally <link href="site:xmlform/step5">Step 5: the Sitemap</link></p>
       </steps>
   
   </howto>
  
  
  
  1.2.4.1   +1 -1      xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step5.xml
  
  Index: step5.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/community/howto/xmlform/step5.xml,v
  retrieving revision 1.2
  retrieving revision 1.2.4.1
  diff -u -r1.2 -r1.2.4.1
  --- step5.xml	6 Jun 2002 14:32:40 -0000	1.2
  +++ step5.xml	5 Jan 2003 16:17:07 -0000	1.2.4.1
  @@ -156,7 +156,7 @@
         <p>build webapp -Dinclude.webapp.libs=true -Dinclude.scratchpad.libs=true webapp</p>
         <p>Place cocoon.war in your webapp folder if you are using Tomcat then restart
Tomcat.</p>
         <p>In a browser go to http://localhost:8080/cocoon/mount/xmlform/howto-wizard.html
and you should see the start page of the mailing list forms.</p>
  -      <p>To return to the <link href="howto-xmlform.html">start</link></p>
  +      <p>To return to the <link href="site:xmlform/intro">start</link></p>
       </steps>
   
   </howto>
  
  
  

Mime
View raw message