forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r357603 [10/11] - in /forrest/site: ./ docs_0_60/ docs_0_60/howto/ docs_0_60/howto/bugzilla-patch/ docs_0_70/ docs_0_70/howto/ docs_0_70/howto/cvs-ssh/ docs_0_80/ docs_0_80/howto/ docs_0_80/howto/cvs-ssh/ dtdx/ pluginDocs/plugins_0_70/ plug...
Date Mon, 19 Dec 2005 01:33:15 GMT
Modified: forrest/site/dtdx/document-v20.html
URL: http://svn.apache.org/viewcvs/forrest/site/dtdx/document-v20.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/dtdx/document-v20.html (original)
+++ forrest/site/dtdx/document-v20.html Sun Dec 18 17:31:25 2005
@@ -384,7 +384,7 @@
 <div class="label">Note</div>
 <div class="content">
       This is a demonstration document using all possible elements in the
-      current Apache Forrest xdocs <span class="codefrag ">document-v20.dtd</span>
+      current Apache Forrest xdocs <span class="codefrag">document-v20.dtd</span>
       (See the <a href="#changes">DTD changes</a> section at the bottom.)
     </div>
 </div>
@@ -400,13 +400,13 @@
 <a name="N1002F"></a><a name="block-inline"></a>
 <h3 class="underlined_5">Block and inline elements</h3>
 <p>This is a simple paragraph. Most documents contain a fair amount of
-        paragraphs. Paragraphs are called <span class="codefrag ">&lt;p&gt;</span>.</p>
-<div class="pre">With the <span class="codefrag ">&lt;p xml:space="preserve"&gt;</span> attribute, you can declare
+        paragraphs. Paragraphs are called <span class="codefrag">&lt;p&gt;</span>.</p>
+<div class="pre">With the <span class="codefrag">&lt;p xml:space="preserve"&gt;</span> attribute, you can declare
         that whitespace should    be   preserved, without implying it is in any other
         way special.</div>
 <p>
         This next paragraph has a class attribute of 'quote'.  CSS can
-        be used to present this <span class="codefrag ">&lt;p class='quote'&gt;</span> in
+        be used to present this <span class="codefrag">&lt;p class='quote'&gt;</span> in
         a different style than the other paragraphs.  The handling of
         this quoted paragraph is defined in the &lt;extra-css&gt;
         element in the skinconf.xml.
@@ -420,27 +420,27 @@
         potatoes, shrimp burger, shrimp sandwich. That- that's about it.
       </p>
 <p>A number of in-line elements are available in the DTD, we will show them
-        inside an unordered list (<span class="codefrag ">&lt;ul&gt;</span>):</p>
+        inside an unordered list (<span class="codefrag">&lt;ul&gt;</span>):</p>
 <ul> 
         
-<li>Here is a simple list item (<span class="codefrag ">&lt;li&gt;</span>).</li> 
+<li>Here is a simple list item (<span class="codefrag">&lt;li&gt;</span>).</li> 
         
-<li>Have you seen the use of the <span class="codefrag ">&lt;code&gt;</span> element in the
+<li>Have you seen the use of the <span class="codefrag">&lt;code&gt;</span> element in the
           previous item?</li> 
         
-<li>Also, we have <span class="codefrag ">&lt;sub&gt;</span> and <span class="codefrag ">&lt;sup&gt;</span>
+<li>Also, we have <span class="codefrag">&lt;sub&gt;</span> and <span class="codefrag">&lt;sup&gt;</span>
           elements to show content <sup>above</sup> or <sub>below</sub> the text
           baseline.</li> 
         
 <li>There is a facility to <em>emphasize</em> certain words using the
-          <span class="codefrag ">&lt;em&gt;</span> <strong><span class="codefrag ">&lt;strong&gt;</span></strong>
+          <span class="codefrag">&lt;em&gt;</span> <strong><span class="codefrag">&lt;strong&gt;</span></strong>
           elements.</li> 
         
 <li>We can use
           <img class="icon" alt="feather" height="22" src="images/icon.png" width="26">
-          <span class="codefrag ">&lt;icon&gt;</span>s too.</li> 
+          <span class="codefrag">&lt;icon&gt;</span>s too.</li> 
         
-<li>Another possibility is the <span class="codefrag ">&lt;img&gt;</span> element:
+<li>Another possibility is the <span class="codefrag">&lt;img&gt;</span> element:
           <img alt="another feather" height="22" src="images/icon.png" width="26">,
           which offers the ability to refer to an image map.</li> 
         
@@ -448,7 +448,7 @@
           <dl> 
             
 <dt>
-<span class="codefrag ">&lt;a href="../index.html"&gt;</span>
+<span class="codefrag">&lt;a href="../index.html"&gt;</span>
 </dt> 
             
 <dd>Use this to
@@ -458,7 +458,7 @@
 
             
 <dt>
-<span class="codefrag ">&lt;a href="#section"&gt;</span>
+<span class="codefrag">&lt;a href="#section"&gt;</span>
 </dt> 
             
 <dd>Use this to
@@ -468,7 +468,7 @@
 
             
 <dt>
-<span class="codefrag ">&lt;a href="../index.html#History"&gt;</span>
+<span class="codefrag">&lt;a href="../index.html#History"&gt;</span>
 </dt> 
             
 <dd>Use this to
@@ -487,7 +487,7 @@
 </li> 
 
         
-<li>Oh, by the way, a definition list <span class="codefrag ">&lt;dl&gt;</span> was used inside
+<li>Oh, by the way, a definition list <span class="codefrag">&lt;dl&gt;</span> was used inside
           the previous list item. We could put another 
           <ul> 
             
@@ -527,24 +527,24 @@
         elements.</p>
 <div class="fixme">
 <div class="label">Fixme (SN)</div>
-<div class="content">The <span class="codefrag ">&lt;fixme&gt;</span> element is used for stuff
-        which still needs work. Mind the <span class="codefrag ">author</span> attribute!</div>
+<div class="content">The <span class="codefrag">&lt;fixme&gt;</span> element is used for stuff
+        which still needs work. Mind the <span class="codefrag">author</span> attribute!</div>
 </div>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">Use the <span class="codefrag ">&lt;note&gt;</span> element to draw attention to something, e.g. ...The <span class="codefrag ">&lt;code&gt;</span> element is used when the author can't
+<div class="content">Use the <span class="codefrag">&lt;note&gt;</span> element to draw attention to something, e.g. ...The <span class="codefrag">&lt;code&gt;</span> element is used when the author can't
         express himself clearly using normal sentences ;-)</div>
 </div>
 <div class="warning">
 <div class="label">Warning</div>
 <div class="content">Sleep deprivation can be the result of being involved in an open
-        source project. (a.k.a. the <span class="codefrag ">&lt;warning&gt;</span> element).
+        source project. (a.k.a. the <span class="codefrag">&lt;warning&gt;</span> element).
       </div>
 </div>
 <div class="note">
 <div class="label">Important</div>
 <div class="content">If you want your own labels for notes and
-        warnings, specify them using the <span class="codefrag ">label</span> attribute.
+        warnings, specify them using the <span class="codefrag">label</span> attribute.
       </div>
 </div>
 <p>Apart from unordered lists, we have ordered lists too, of course.</p>
@@ -654,7 +654,7 @@
 <a name="N101C9"></a><a name="source"></a>
 <h3 class="underlined_5">Showing preformatted source code</h3>
 <p>Enough about these sections. Let's have a look at more interesting
-          elements, <span class="codefrag ">&lt;source&gt;</span> for instance:</p>
+          elements, <span class="codefrag">&lt;source&gt;</span> for instance:</p>
 <pre class="code">
 // This example is from the book _Java in a Nutshell_ by David Flanagan.
 // Written by David Flanagan.  Copyright (c) 1996 O'Reilly &amp; Associates.
@@ -672,9 +672,9 @@
     }
 }</pre>
 <p>CDATA sections are used within 
-          <span class="codefrag ">&lt;source&gt;</span> elements so that you can write pointy
+          <span class="codefrag">&lt;source&gt;</span> elements so that you can write pointy
            brackets without needing to escape them with messy
-          <span class="codefrag ">&amp;lt;</span> entities ...
+          <span class="codefrag">&amp;lt;</span> entities ...
         </p>
 <pre class="code">
 &lt;pointy&gt;
@@ -745,9 +745,9 @@
 </table>
 <a name="second-figure-anchor" id="second-figure-anchor"></a><a name="N10251"></a><a name="figure"></a>
 <h3 class="underlined_5">Using figures</h3>
-<p>And a <span class="codefrag ">&lt;figure&gt;</span> to end all of this.
+<p>And a <span class="codefrag">&lt;figure&gt;</span> to end all of this.
           Note that this can also be implemented with an
-          <span class="codefrag ">&lt;img&gt;</span> element.
+          <span class="codefrag">&lt;img&gt;</span> element.
         </p>
 <div id="" style="text-align: center;">
 <img id="" class="figure" alt="The fine Forrest logo" src="images/project-logo.png" height="65" width="220"></div>

Modified: forrest/site/dtdx/dtd-docs.html
URL: http://svn.apache.org/viewcvs/forrest/site/dtdx/dtd-docs.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/dtdx/dtd-docs.html (original)
+++ forrest/site/dtdx/dtd-docs.html Sun Dec 18 17:31:25 2005
@@ -345,7 +345,7 @@
         do not reflect the modularity of our DTDs, they are primarily
         "user-oriented help" documentation.</p>
 <p>The actual DTDs are located in the Forrest distribution at
-        <span class="codefrag ">main/webapp/resources/schema/</span>
+        <span class="codefrag">main/webapp/resources/schema/</span>
 </p>
 </div>
     

Modified: forrest/site/forrest-friday.html
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-friday.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/forrest-friday.html (original)
+++ forrest/site/forrest-friday.html Sun Dec 18 17:31:25 2005
@@ -317,12 +317,12 @@
         </li>
         
 <li>
-          Set the channel mode: <span class="codefrag ">/mode +n</span>
+          Set the channel mode: <span class="codefrag">/mode +n</span>
         
 </li>
         
 <li>
-          Declare today's topic: <span class="codefrag ">/topic ForrestFriday: XHTML2 core and Jira cleanup</span>
+          Declare today's topic: <span class="codefrag">/topic ForrestFriday: XHTML2 core and Jira cleanup</span>
         
 </li>
         

Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-issues.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Sun Dec 18 17:31:25 2005
@@ -186,79 +186,79 @@
 <div id="minitoc-area">
 <ul class="minitoc">
 <li>
-<a href="#%5BFOR-144%5D+define+new+format+for+skinconf.xml">[FOR-144] define new format for skinconf.xml</a>
-</li>
-<li>
 <a href="#%5BFOR-713%5D+HTML-to-document.xsl+no+longer+generates+an+XDoc">[FOR-713] HTML-to-document.xsl no longer generates an XDoc</a>
 </li>
 <li>
 <a href="#%5BFOR-591%5D+MaxMemory+needs+increasing">[FOR-591] MaxMemory needs increasing</a>
 </li>
 <li>
-<a href="#%5BFOR-588%5D+Design+new+configuration+system">[FOR-588] Design new configuration system</a>
+<a href="#%5BFOR-762%5D+Default+page+URL+for+breadcrumbs+and+site%3A+links">[FOR-762] Default page URL for breadcrumbs and site: links</a>
 </li>
 <li>
-<a href="#%5BFOR-572%5D+run+a+memory+profiler+while+forrest+is+operating">[FOR-572] run a memory profiler while forrest is operating</a>
+<a href="#%5BFOR-707%5D+Document+i18n+features+of+Forrest">[FOR-707] Document i18n features of Forrest</a>
 </li>
 <li>
-<a href="#%5BFOR-701%5D+Missing+locationmap+entry+gives+poor+error">[FOR-701] Missing locationmap entry gives poor error</a>
+<a href="#%5BFOR-711%5D+Cache+results+from+the+Locationmap">[FOR-711] Cache results from the Locationmap</a>
 </li>
 <li>
-<a href="#%5BFOR-654%5D+Create+Schema+for+XHTML2+subset">[FOR-654] Create Schema for XHTML2 subset</a>
+<a href="#%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo">[FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo</a>
 </li>
 <li>
-<a href="#%5BFOR-707%5D+Document+i18n+features+of+Forrest">[FOR-707] Document i18n features of Forrest</a>
+<a href="#%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode">[FOR-735] Plugins are not correctly deployed in webapp mode</a>
 </li>
 <li>
-<a href="#%5BFOR-630%5D+Forrest+strategy+and+direction">[FOR-630] Forrest strategy and direction</a>
+<a href="#%5BFOR-388%5D+Use+plugins+in-place+if+src+available">[FOR-388] Use plugins in-place if src available</a>
 </li>
 <li>
-<a href="#%5BFOR-675%5D+upgrading+to+commons-jxpath-1.2.jar+causes+failures+with+linkrewriter+protocols+site%3A+etc.">[FOR-675] upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc.</a>
+<a href="#%5BFOR-748%5D+forrest+war%3A+Cannot+load+%27resource%3A%2F%2Fplugins.xconf+...+WEB-INF%2Fcocoon.xconf">[FOR-748] forrest war: Cannot load 'resource://plugins.xconf ... WEB-INF/cocoon.xconf</a>
 </li>
 <li>
-<a href="#%5BFOR-711%5D+Cache+results+from+the+Locationmap">[FOR-711] Cache results from the Locationmap</a>
+<a href="#%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes">[FOR-241] character entities (e.g. ampersand) are expanded again for href or src attributes</a>
 </li>
 <li>
-<a href="#%5BFOR-388%5D+Use+plugins+in-place+if+src+available">[FOR-388] Use plugins in-place if src available</a>
+<a href="#%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs">[FOR-209] First level selected tab is not highlighted when containing 2nd level tabs</a>
 </li>
 <li>
-<a href="#%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo">[FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo</a>
+<a href="#%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links">[FOR-211] whole-site html and pdf: broken ext links</a>
 </li>
 <li>
-<a href="#%5BFOR-748%5D+forrest+war%3A+Cannot+load+%27resource%3A%2F%2Fplugins.xconf+...+WEB-INF%2Fcocoon.xconf">[FOR-748] forrest war: Cannot load 'resource://plugins.xconf ... WEB-INF/cocoon.xconf</a>
+<a href="#%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately">[FOR-203] 2nd level tabs are not selected appropriately</a>
 </li>
 <li>
-<a href="#%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode">[FOR-735] Plugins are not correctly deployed in webapp mode</a>
+<a href="#%5BFOR-546%5D+Sitemap+reference+doc+should+be+updated+to+reflect+plugin+architecture">[FOR-546] Sitemap reference doc should be updated to reflect plugin architecture</a>
 </li>
 <li>
-<a href="#%5BFOR-490%5D+serve+multiple+sites+on+a+single+Forrest+instance">[FOR-490] serve multiple sites on a single Forrest instance</a>
+<a href="#%5BFOR-560%5D+Remove+duplicate+jars+from+eclipse+plugins">[FOR-560] Remove duplicate jars from eclipse plugins</a>
 </li>
 <li>
-<a href="#%5BFOR-343%5D+Upgrading+Plugins">[FOR-343] Upgrading Plugins</a>
+<a href="#%5BFOR-562%5D+Update+Plugins+howto">[FOR-562] Update Plugins howto</a>
 </li>
 <li>
-<a href="#%5BFOR-284%5D+link+rewriting+broken+when+linking+to+xml+source+views+which+contain+site%3A+links">[FOR-284] link rewriting broken when linking to xml source views which contain site: links</a>
+<a href="#%5BFOR-677%5D+leading+slash+in+gathered+URIs+causes+double+the+number+of+links+to+be+processed">[FOR-677] leading slash in gathered URIs causes double the number of links to be processed</a>
 </li>
 <li>
-<a href="#%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes">[FOR-241] character entities (e.g. ampersand) are expanded again for href or src attributes</a>
+<a href="#%5BFOR-705%5D+Target+of+LocationMap+rewriteDemo+causes+build+failure+when+target+not+available">[FOR-705] Target of LocationMap rewriteDemo causes build failure when target not available</a>
 </li>
 <li>
-<a href="#%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs">[FOR-209] First level selected tab is not highlighted when containing 2nd level tabs</a>
+<a href="#%5BFOR-721%5D+entries+without+labels+in+site.xml+are+now+being+crawled+and+generated">[FOR-721] entries without labels in site.xml are now being crawled and generated</a>
 </li>
 <li>
-<a href="#%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links">[FOR-211] whole-site html and pdf: broken ext links</a>
+<a href="#%5BFOR-699%5D+Beginner+HowTos+for+installing+Forrest">[FOR-699] Beginner HowTos for installing Forrest</a>
 </li>
 <li>
-<a href="#%5BFOR-215%5D+site.lucene+name+colaps+with+site.html+request">[FOR-215] site.lucene name colaps with site.html request</a>
+<a href="#%5BFOR-644%5D+whitespace+cleanup">[FOR-644] whitespace cleanup</a>
 </li>
 <li>
-<a href="#%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately">[FOR-203] 2nd level tabs are not selected appropriately</a>
+<a href="#%5BFOR-645%5D+patches+for+whitespace+cleanup">[FOR-645] patches for whitespace cleanup</a>
 </li>
 <li>
-<a href="#%5BFOR-184%5D+Switch+to+XHTML2">[FOR-184] Switch to XHTML2</a>
+<a href="#%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links">[FOR-210] whole-site html and pdf: broken link faq, broken image links</a>
 </li>
 <li>
-<a href="#%5BFOR-187%5D+Redefine+project+documentation+dirs">[FOR-187] Redefine project documentation dirs</a>
+<a href="#%5BFOR-200%5D+Locationmap+for+Forrest+and+Users">[FOR-200] Locationmap for Forrest and Users</a>
+</li>
+<li>
+<a href="#%5BFOR-726%5D+use+locationmap+in+all+of+the+plugins">[FOR-726] use locationmap in all of the plugins</a>
 </li>
 </ul>
 </div>
@@ -270,25 +270,7 @@
        <a href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?pid=12310000&resolutionIds=-1&tempMax=1000&reset=true">all</a> open issues).
       The listing below is regenerated on each Forrest run.</div>
 </div>
-<a name="N10011"></a><a name="%5BFOR-144%5D+define+new+format+for+skinconf.xml"></a>
-<h2 class="underlined_10">[FOR-144] define new format for skinconf.xml</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-144">http://issues.apache.org/jira/browse/FOR-144</a>
-</p>
-<p>We are attempting to define a new extensible skinconf format. Here is one thread where the discussion is happening (there were some other threads leading up to that).
-&lt;br&gt;
-&lt;a href="http://marc.theaimsgroup.com/?t=108315759100005"&gt;http://marc.theaimsgroup.com/?t=108315759100005&lt;/a&gt;
-&lt;br&gt;
-
-&lt;br&gt;
-
-&lt;br&gt;
-
-&lt;br&gt;
-</p>
-</div>
-<a name="N1001F"></a><a name="%5BFOR-713%5D+HTML-to-document.xsl+no+longer+generates+an+XDoc"></a>
+<a name="N10011"></a><a name="%5BFOR-713%5D+HTML-to-document.xsl+no+longer+generates+an+XDoc"></a>
 <h2 class="underlined_10">[FOR-713] HTML-to-document.xsl no longer generates an XDoc</h2>
 <div class="section">
 <p>
@@ -304,7 +286,7 @@
 &lt;br&gt;
 </p>
 </div>
-<a name="N1002D"></a><a name="%5BFOR-591%5D+MaxMemory+needs+increasing"></a>
+<a name="N1001F"></a><a name="%5BFOR-591%5D+MaxMemory+needs+increasing"></a>
 <h2 class="underlined_10">[FOR-591] MaxMemory needs increasing</h2>
 <div class="section">
 <p>
@@ -324,45 +306,39 @@
 &lt;br&gt;
 (NB maxmemory has been increased in forrest.properties, if we resolve this issue it should be reduced again)</p>
 </div>
-<a name="N1003B"></a><a name="%5BFOR-588%5D+Design+new+configuration+system"></a>
-<h2 class="underlined_10">[FOR-588] Design new configuration system</h2>
+<a name="N1002D"></a><a name="%5BFOR-762%5D+Default+page+URL+for+breadcrumbs+and+site%3A+links"></a>
+<h2 class="underlined_10">[FOR-762] Default page URL for breadcrumbs and site: links</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-588">http://issues.apache.org/jira/browse/FOR-588</a>
+<a href="http://issues.apache.org/jira/browse/FOR-762">http://issues.apache.org/jira/browse/FOR-762</a>
 </p>
-<p>We need a new config system for Forrest for various reasons: the initial config system was known to be limited; to enable the specification of multiple Forrest sites within a single instance of Forrest; to accommodate the changes brought about by forrest:views, themes, and plugins.</p>
-</div>
-<a name="N10049"></a><a name="%5BFOR-572%5D+run+a+memory+profiler+while+forrest+is+operating"></a>
-<h2 class="underlined_10">[FOR-572] run a memory profiler while forrest is operating</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-572">http://issues.apache.org/jira/browse/FOR-572</a>
-</p>
-<p>We need to run a memory profiler while forrest is operating.</p>
-</div>
-<a name="N10057"></a><a name="%5BFOR-701%5D+Missing+locationmap+entry+gives+poor+error"></a>
-<h2 class="underlined_10">[FOR-701] Missing locationmap entry gives poor error</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-701">http://issues.apache.org/jira/browse/FOR-701</a>
-</p>
-<p>If there is no locationmap entry for a resource we get a &amp;quot;resource not found&amp;quot; error. This is fine if it is the actual source file that is missing. However, now that we are using the LM to find other intermediate resources, such as stylesheets etc. it can be misleading.
+<p>When employing breadcrumbs,
 &lt;br&gt;
 
 &lt;br&gt;
-We need to throw a meaningful error when when a resource cannot be found.</p>
-</div>
-<a name="N10065"></a><a name="%5BFOR-654%5D+Create+Schema+for+XHTML2+subset"></a>
-<h2 class="underlined_10">[FOR-654] Create Schema for XHTML2 subset</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-654">http://issues.apache.org/jira/browse/FOR-654</a>
-</p>
-<p>We need a RelaxNG schema for the subset of XHTML identified in:
+example generated links:  home &amp;gt; dir &amp;gt; subdir
+&lt;br&gt;
+
+&lt;br&gt;
+if the user is in node subdir, then clicks dir,
+&lt;br&gt;
+cocoon returns &amp;quot;The requested resource &amp;quot;/dir /&amp;quot; could not be found.
+&lt;br&gt;
+The link's absolute path during testing is &lt;a href="http://localhost:8888/dir/"&gt;http://localhost:8888/dir/&lt;/a&gt;
+&lt;br&gt;
+Case 1. If you place an index.html file under &lt;a href="http://localhost:8888/dir/"&gt;http://localhost:8888/dir/&lt;/a&gt; for a redirect or viewable content,
+&lt;br&gt;
+clicking on breadcrumbs'  dir link throws the error.
+&lt;br&gt;
+Case 2. If you manually enter the index.html in the browser path after &lt;a href="http://localhost:8888/dir/,"&gt;http://localhost:8888/dir/,&lt;/a&gt; the request is handled.
+&lt;br&gt;
+Case 3. If sitemap has match=&amp;quot;dir/index.html&amp;quot;, cocoon still isn't happy with request dir/
 &lt;br&gt;
-&lt;a href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=112489488330888&amp;w=2"&gt;http://marc.theaimsgroup.com/?l=forrest-dev&amp;amp;m=112489488330888&amp;amp;w=2&lt;/a&gt;</p>
+
+&lt;br&gt;
+Cocoon does not appear to assume the end node directory is index.* and thus appends no file automatically as tomcat or the http server does so it must be manually done. </p>
 </div>
-<a name="N10073"></a><a name="%5BFOR-707%5D+Document+i18n+features+of+Forrest"></a>
+<a name="N1003B"></a><a name="%5BFOR-707%5D+Document+i18n+features+of+Forrest"></a>
 <h2 class="underlined_10">[FOR-707] Document i18n features of Forrest</h2>
 <div class="section">
 <p>
@@ -382,417 +358,357 @@
 &lt;br&gt;
 We could, at the very least use the locationmap to pull this content into our site [OT: I wonder if this could be a way to generate more documentation?)</p>
 </div>
-<a name="N10081"></a><a name="%5BFOR-630%5D+Forrest+strategy+and+direction"></a>
-<h2 class="underlined_10">[FOR-630] Forrest strategy and direction</h2>
+<a name="N10049"></a><a name="%5BFOR-711%5D+Cache+results+from+the+Locationmap"></a>
+<h2 class="underlined_10">[FOR-711] Cache results from the Locationmap</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-630">http://issues.apache.org/jira/browse/FOR-630</a>
+<a href="http://issues.apache.org/jira/browse/FOR-711">http://issues.apache.org/jira/browse/FOR-711</a>
 </p>
-<p>Topics for discussion gathered at ApacheCon EU 2005.
-&lt;br&gt;
-
-&lt;br&gt;
-WARNING: Only reply to the general theme of this
-&lt;br&gt;
-topics list. Please create separate threads for
-&lt;br&gt;
-each specific topic.
+<p>Now that we are using the locationmap extensively it is showing up just how innefficient it is. The problem is that for the majority of requests there are multiple reqeuests to the locationmap. We can make things much faster (especially on the first page request) by caching results in the locationmap.
 &lt;br&gt;
 
 &lt;br&gt;
-Actually we should be using Jira for some of this.
-&lt;br&gt;
-How about discussing on the mailing list, and
-&lt;br&gt;
-putting summaries into Jira.
+I think a simple cache will sufice, lets just provide a static hashmap using the hint as a key and, of course, the location as the value.
 &lt;br&gt;
 
 &lt;br&gt;
-I have the scraps of paper that Nicola Ken wrote.
-&lt;br&gt;
-Photographs are in:
-&lt;br&gt;
-&lt;a href="http://svn.apache.org/repos/asf/forrest/events/apachecon-eu-2005"&gt;http://svn.apache.org/repos/asf/forrest/events/apachecon-eu-2005&lt;/a&gt;
-&lt;br&gt;
-Ross helped me to interpret some of the sqwiggles,
-&lt;br&gt;
-but there are still some obscure parts (marked
-&lt;br&gt;
-with #? below). The items are raw, i have not tried
-&lt;br&gt;
-to explain any or add others.
+If we test all locationmaps and find no result we should record that tere is no result in this hashmap. This will also be a good place to throw an exception so that Cocoon can better report such errors (see FOR-701)</p>
+</div>
+<a name="N10057"></a><a name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
+<h2 class="underlined_10">[FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-742">http://issues.apache.org/jira/browse/FOR-742</a>
+</p>
+<p>The plugin retrieval and deployment process are not quite correct. Recently the projectInfo plugin had its version number incremented and the &amp;quot;unversioned&amp;quot; plugin now relates specifically to 0.8-dev version. That prevents 0.7 from accessing the relevant plugin.
 &lt;br&gt;
 
 &lt;br&gt;
-List of topics is in no particular order and
-&lt;br&gt;
-it is not complete. We spent maybe 15 minutes
-&lt;br&gt;
-brainstorming. We had a first quick pass at
+The solution is discussed here:
 &lt;br&gt;
-assigning some priority.
+&lt;a href="http://marc.theaimsgroup.com/?t=113176328300002"&gt;http://marc.theaimsgroup.com/?t=113176328300002&lt;/a&gt;</p>
+</div>
+<a name="N10065"></a><a name="%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode"></a>
+<h2 class="underlined_10">[FOR-735] Plugins are not correctly deployed in webapp mode</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-735">http://issues.apache.org/jira/browse/FOR-735</a>
+</p>
+<p>(At this point I didn't try this scenario step by step any more; basically it is what we did to setup the site, except that we copied our project data from forrest 0.6 before trying the pdf links)
 &lt;br&gt;
 
 &lt;br&gt;
-I don't understand NKBs priority symbols.
-&lt;br&gt;
-Anyway some items where marked with
-&lt;br&gt;
-&amp;nbsp;circle ... [C]
-&lt;br&gt;
-&amp;nbsp;square ... [S]
-&lt;br&gt;
-
+- run forrest webapp to create an empty webapp
 &lt;br&gt;
-Then we went straight on to the top topic:
+- configure Tomcat to run the webapp (we did it by creating a context descriptor and put it onder Tomcat's config directory)
 &lt;br&gt;
-&amp;quot;configuration&amp;quot; and spent the rest of the day.
+- the pdf links give an error &amp;quot;Resource Not Found&amp;quot;</p>
+</div>
+<a name="N10073"></a><a name="%5BFOR-388%5D+Use+plugins+in-place+if+src+available"></a>
+<h2 class="underlined_10">[FOR-388] Use plugins in-place if src available</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-388">http://issues.apache.org/jira/browse/FOR-388</a>
+</p>
+<p>At present Forrest will attempt to download plugins even if they are available in src form in the local filesystem as part of an SVN checkout.
 &lt;br&gt;
 
 &lt;br&gt;
---------------
+Have Forrest mount plugins from designated directories in preference to downloading them wherever possible (need more than posible location for src plugins as some people may be developing their own plugins outside of Forrest)
 &lt;br&gt;
 
 &lt;br&gt;
-* Create lenya/forrest publication.
-&lt;br&gt;
-
+</p>
+</div>
+<a name="N10081"></a><a name="%5BFOR-748%5D+forrest+war%3A+Cannot+load+%27resource%3A%2F%2Fplugins.xconf+...+WEB-INF%2Fcocoon.xconf"></a>
+<h2 class="underlined_10">[FOR-748] forrest war: Cannot load 'resource://plugins.xconf ... WEB-INF/cocoon.xconf</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-748">http://issues.apache.org/jira/browse/FOR-748</a>
+</p>
+<p>Doing 'forrest war' and copy to a full Jetty/webapps/ and start Jetty, then get this error on Jetty startup ...
 &lt;br&gt;
-* [C] Naming convention for &amp;quot;views&amp;quot;.
+Cannot load '&lt;a href="resource://plugins.xconf"&gt;resource://plugins.xconf&lt;/a&gt;' at ... webapp/WEB-INF/cocoon.xconf:31:44</p>
+</div>
+<a name="N1008F"></a><a name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
+<h2 class="underlined_10">[FOR-241] character entities (e.g. ampersand) are expanded again for href or src attributes</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-241">http://issues.apache.org/jira/browse/FOR-241</a>
+</p>
+<p>If I have a url like this inside the XML source:
 &lt;br&gt;
 
 &lt;br&gt;
-* Roadmap specifically for views.
+&lt;a href="http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;type=1"&gt;http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;amp;type=1&lt;/a&gt;
 &lt;br&gt;
 
 &lt;br&gt;
-* [S] i18n support with locationmap.
-&lt;br&gt;
-
+validate-xdocs fails because it wants the literal &amp;amp; to be typed out as
 &lt;br&gt;
-* Locationmap - what is needed to complete it.
+&amp;amp; instead. So I correct it to become:
 &lt;br&gt;
 
 &lt;br&gt;
-* [C] Configuration |=&amp;gt; apache      #? arrow apache #?
+&lt;a href="http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;type=1"&gt;http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;amp;type=1&lt;/a&gt;
 &lt;br&gt;
 
 &lt;br&gt;
-* TraversableSource ...
+However, the generated HTML has the entity resolution UNDONE!:
 &lt;br&gt;
 
 &lt;br&gt;
-&amp;nbsp;&amp;nbsp;* Source resolving for locationmap.
+&lt;a href="http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;type=1"&gt;http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;amp;type=1&lt;/a&gt;
 &lt;br&gt;
 
 &lt;br&gt;
-&amp;nbsp;&amp;nbsp;* [C] How views are interacting with locationmap?
+This HTML fails validation as 4.01 transitional.
 &lt;br&gt;
 
 &lt;br&gt;
-* [S] Documentation mismatch. Docs are distributed in
-&lt;br&gt;
-&amp;nbsp;&amp;nbsp;various places: site, plugins, seed.
+David Crossley adds:
 &lt;br&gt;
-
+There is a demonstration of the problem in the document
 &lt;br&gt;
-* Block documentation for Cocoon (/Forrest).
+src/documentation/content/xdocs/docs/dreams.xml
 &lt;br&gt;
-
+The ampersand in the link element text is properly handled but
 &lt;br&gt;
-* [C] Pre-processing plugins.
+the ampersand in the link href attribute is not.</p>
+</div>
+<a name="N1009D"></a><a name="%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs"></a>
+<h2 class="underlined_10">[FOR-209] First level selected tab is not highlighted when containing 2nd level tabs</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-209">http://issues.apache.org/jira/browse/FOR-209</a>
+</p>
+<p>When there are two levels of tabs, the selected first level tab does not get highlighted, nor are there any other visual or structural clues as to which first-level tab is active, and which contains the displayed 2nd level tabs.
 &lt;br&gt;
 
 &lt;br&gt;
-* Flow of the plugin process.
-&lt;br&gt;
-&amp;nbsp;&amp;nbsp;plugins - locationmap / flow   #? this line obscure #?
-&lt;br&gt;
-
+This is checked with both the default skin, and with tigris-style.
 &lt;br&gt;
-* Memory profiling.
+</p>
+</div>
+<a name="N100AB"></a><a name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
+<h2 class="underlined_10">[FOR-211] whole-site html and pdf: broken ext links</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-211">http://issues.apache.org/jira/browse/FOR-211</a>
+</p>
+<p>In the the generated site.html all of the external links are broken (i.e. the href attributes are like ... error:#ext:forrest).</p>
+</div>
+<a name="N100B9"></a><a name="%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately"></a>
+<h2 class="underlined_10">[FOR-203] 2nd level tabs are not selected appropriately</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-203">http://issues.apache.org/jira/browse/FOR-203</a>
+</p>
+<p>The 2nd level tabs are not shown for menu entries that caused the issue FOR-111. This happens because the starts-with() path comparison fails for menu entries that do not reside the same directory as is specified in the &amp;quot;dir&amp;quot; attribute of the 2nd level tabs.
 &lt;br&gt;
 
 &lt;br&gt;
-* Better use of Jira.
+See the attached bug-demo.tgz for an example. Select &amp;quot;Samples/Apache document&amp;quot; and notice that the 2nd level tabs are shown. Now select &amp;quot;Samples/BUG DEMO&amp;quot; and notice that the 2nd level tabs are not shown.
 &lt;br&gt;
 
 &lt;br&gt;
-* [S] XHTML2 transition.
+This is because the document corresponding to &amp;quot;Samples/Apache document&amp;quot; resides in the directory &amp;quot;/samples&amp;quot; whereas the document corresponding to &amp;quot;Samples/BUG DEMO&amp;quot; resides in the directory &amp;quot;/bug-sample&amp;quot;.
 &lt;br&gt;
 
 &lt;br&gt;
-* [S] Live Forrest for Apache.
+Kind regards,
 &lt;br&gt;
-&amp;nbsp;&amp;nbsp;(a configuration usecase)
+&amp;nbsp;&amp;nbsp;Lorenz Froihofer.</p>
+</div>
+<a name="N100C7"></a><a name="%5BFOR-546%5D+Sitemap+reference+doc+should+be+updated+to+reflect+plugin+architecture"></a>
+<h2 class="underlined_10">[FOR-546] Sitemap reference doc should be updated to reflect plugin architecture</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-546">http://issues.apache.org/jira/browse/FOR-546</a>
+</p>
+<p>The example at &lt;a href="http://forrest.apache.org/0.7/docs/sitemap-ref.html#pdf"&gt;http://forrest.apache.org/0.7/docs/sitemap-ref.html#pdf&lt;/a&gt; uses a fo2pdf serializer.  This probaly worked in versions &amp;lt; 0.7, because the PDF output feature was in the core, and the serializer was very likely declared there.
 &lt;br&gt;
 
 &lt;br&gt;
-* [S] New skins for views.
+With version 0.7, PDF output is moved to a plugin, the fo2pdf serializer seems to be no longer there.  The serializer should probably be added to the example, for completeness.
 &lt;br&gt;
 
 &lt;br&gt;
-* Views ... body=&amp;quot;true|false&amp;quot; head=&amp;quot;true|false&amp;quot;
+&amp;nbsp;&amp;nbsp;&amp;lt;map:components&amp;gt;
 &lt;br&gt;
-
+&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;map:serializers&amp;gt;
 &lt;br&gt;
-* The *.ft files in a plugin (one-to-many).
-&lt;br&gt;
-
+&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;map:serializer name=&amp;quot;fo2pdf&amp;quot;
 &lt;br&gt;
-* Move into Java -&amp;gt; 0.9.5 or when needed.  #? no idea what #?
+&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;src=&amp;quot;org.apache.cocoon.serialization.FOPSerializer&amp;quot;
 &lt;br&gt;
-&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
+&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;mime-type=&amp;quot;application/pdf&amp;quot;/&amp;gt;
 &lt;br&gt;
-* [C] View / doctypes.
+&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;/map:serializers&amp;gt;
 &lt;br&gt;
-&amp;nbsp;&amp;nbsp;(view in view)
+&amp;nbsp;&amp;nbsp;&amp;lt;/map:components&amp;gt;
 &lt;br&gt;
 
 &lt;br&gt;
-* [C] Content directory.</p>
+I found out about this because my sitemap uses the fo2pdf too (docbook to PDF), and had to add the serializer.</p>
 </div>
-<a name="N1008F"></a><a name="%5BFOR-675%5D+upgrading+to+commons-jxpath-1.2.jar+causes+failures+with+linkrewriter+protocols+site%3A+etc."></a>
-<h2 class="underlined_10">[FOR-675] upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc.</h2>
+<a name="N100D5"></a><a name="%5BFOR-560%5D+Remove+duplicate+jars+from+eclipse+plugins"></a>
+<h2 class="underlined_10">[FOR-560] Remove duplicate jars from eclipse plugins</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-675">http://issues.apache.org/jira/browse/FOR-675</a>
+<a href="http://issues.apache.org/jira/browse/FOR-560">http://issues.apache.org/jira/browse/FOR-560</a>
 </p>
-<p>upgrading from commons-jxpath-20030909.jar to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc. This happens in both modes: 'forret run' and 'forrest'.</p>
+<p>tools/eclipse/plugins/org.apache.forrest.eclipse.servletEngine/lib contains some duplicate jars to those in the main Forrest trunk. We should find a way of reusing the jars from their existing location.</p>
 </div>
-<a name="N1009D"></a><a name="%5BFOR-711%5D+Cache+results+from+the+Locationmap"></a>
-<h2 class="underlined_10">[FOR-711] Cache results from the Locationmap</h2>
+<a name="N100E3"></a><a name="%5BFOR-562%5D+Update+Plugins+howto"></a>
+<h2 class="underlined_10">[FOR-562] Update Plugins howto</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-711">http://issues.apache.org/jira/browse/FOR-711</a>
+<a href="http://issues.apache.org/jira/browse/FOR-562">http://issues.apache.org/jira/browse/FOR-562</a>
 </p>
-<p>Now that we are using the locationmap extensively it is showing up just how innefficient it is. The problem is that for the majority of requests there are multiple reqeuests to the locationmap. We can make things much faster (especially on the first page request) by caching results in the locationmap.
+<p>The document at &lt;a href="http://forrest.apache.org/docs_0_70/howto/howto-buildPlugin.html"&gt;http://forrest.apache.org/docs_0_70/howto/howto-buildPlugin.html&lt;/a&gt; needs to be updated in the following ways:
 &lt;br&gt;
 
 &lt;br&gt;
-I think a simple cache will sufice, lets just provide a static hashmap using the hint as a key and, of course, the location as the value.
+- remove warnings about instability
 &lt;br&gt;
-
+- add details about creating plugins outside of FORREST_HOME (mkdir PROJECT_HOME/plugins, copy whiteboard/plugins/build.xml to PROJECT_HOME/plugins, edit forrest.plugins.dir property)
 &lt;br&gt;
-If we test all locationmaps and find no result we should record that tere is no result in this hashmap. This will also be a good place to throw an exception so that Cocoon can better report such errors (see FOR-701)</p>
-</div>
-<a name="N100AB"></a><a name="%5BFOR-388%5D+Use+plugins+in-place+if+src+available"></a>
-<h2 class="underlined_10">[FOR-388] Use plugins in-place if src available</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-388">http://issues.apache.org/jira/browse/FOR-388</a>
-</p>
-<p>At present Forrest will attempt to download plugins even if they are available in src form in the local filesystem as part of an SVN checkout.
-&lt;br&gt;
-
+- update section on seeding a plugin to reflect working outside of FORREST_HOME
 &lt;br&gt;
-Have Forrest mount plugins from designated directories in preference to downloading them wherever possible (need more than posible location for src plugins as some people may be developing their own plugins outside of Forrest)
+- remove the existing note about copying build.xml
 &lt;br&gt;
 
 &lt;br&gt;
-</p>
-</div>
-<a name="N100B9"></a><a name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
-<h2 class="underlined_10">[FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-742">http://issues.apache.org/jira/browse/FOR-742</a>
-</p>
-<p>The plugin retrieval and deployment process are not quite correct. Recently the projectInfo plugin had its version number incremented and the &amp;quot;unversioned&amp;quot; plugin now relates specifically to 0.8-dev version. That prevents 0.7 from accessing the relevant plugin.
+NB here should be no need to edit the forrest.plugins.dir, simply set it to '.'
 &lt;br&gt;
-
+In addition the buil file template should really be provided from the plugins directory rather than the whiteboard dir
 &lt;br&gt;
-The solution is discussed here:
+
 &lt;br&gt;
-&lt;a href="http://marc.theaimsgroup.com/?t=113176328300002"&gt;http://marc.theaimsgroup.com/?t=113176328300002&lt;/a&gt;</p>
-</div>
-<a name="N100C7"></a><a name="%5BFOR-748%5D+forrest+war%3A+Cannot+load+%27resource%3A%2F%2Fplugins.xconf+...+WEB-INF%2Fcocoon.xconf"></a>
-<h2 class="underlined_10">[FOR-748] forrest war: Cannot load 'resource://plugins.xconf ... WEB-INF/cocoon.xconf</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-748">http://issues.apache.org/jira/browse/FOR-748</a>
 </p>
-<p>Doing 'forrest war' and copy to a full Jetty/webapps/ and start Jetty, then get this error on Jetty startup ...
-&lt;br&gt;
-Cannot load '&lt;a href="resource://plugins.xconf"&gt;resource://plugins.xconf&lt;/a&gt;' at ... webapp/WEB-INF/cocoon.xconf:31:44</p>
 </div>
-<a name="N100D5"></a><a name="%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode"></a>
-<h2 class="underlined_10">[FOR-735] Plugins are not correctly deployed in webapp mode</h2>
+<a name="N100F1"></a><a name="%5BFOR-677%5D+leading+slash+in+gathered+URIs+causes+double+the+number+of+links+to+be+processed"></a>
+<h2 class="underlined_10">[FOR-677] leading slash in gathered URIs causes double the number of links to be processed</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-735">http://issues.apache.org/jira/browse/FOR-735</a>
+<a href="http://issues.apache.org/jira/browse/FOR-677">http://issues.apache.org/jira/browse/FOR-677</a>
 </p>
-<p>(At this point I didn't try this scenario step by step any more; basically it is what we did to setup the site, except that we copied our project data from forrest 0.6 before trying the pdf links)
+<p>Doing 'forrest' starts at the virtual document called linkmap.html where the Cocoon crawler gathers the initial set of links, then starts crawling and generating pages. Any new links are pushed onto the linkmap. However, for some sites, such as our own &amp;quot;seed-sample&amp;quot; and our &amp;quot;site-author&amp;quot;, there is a sudden jump in the number of URIs remaining to be processed.
 &lt;br&gt;
 
 &lt;br&gt;
-- run forrest webapp to create an empty webapp
+This is due to a URI with a leading slash (e.g. /samples/faq.html). When that URI is processed, it gains a whole new set of links all with leading slashes, and so the list of URIs is potentially doubled.
 &lt;br&gt;
-- configure Tomcat to run the webapp (we did it by creating a context descriptor and put it onder Tomcat's config directory)
-&lt;br&gt;
-- the pdf links give an error &amp;quot;Resource Not Found&amp;quot;</p>
-</div>
-<a name="N100E3"></a><a name="%5BFOR-490%5D+serve+multiple+sites+on+a+single+Forrest+instance"></a>
-<h2 class="underlined_10">[FOR-490] serve multiple sites on a single Forrest instance</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-490">http://issues.apache.org/jira/browse/FOR-490</a>
-</p>
-<p>Nicola Ken Barozzi wrote:&lt;br&gt;
-&amp;gt; After that, it would be beneficial to be able to serve &lt;br&gt;
-&amp;gt; multiple sites on  a single Forrest instance, so that we &lt;br&gt;
-&amp;gt; can have other projects join and &lt;br&gt;
-&amp;gt; have their site served.&lt;br&gt;
-&lt;br&gt;
-This last point (seving multiple &amp;quot;sites&amp;quot; from one Forrest&lt;br&gt;
-instance) is important even without moving Forrest to a&lt;br&gt;
-live server (I'm +1 on this).&lt;br&gt;
+
 &lt;br&gt;
-Right now we have various styleguides in Forrest and if&lt;br&gt;
-I need to run them at once I have to start Forrest/jetty&lt;br&gt;
-with different ports.&lt;br&gt;
+This issue could be due to a user error, i.e. adding a link that deliberately begins with a slash. Sometimes, that is unavoidable.
 &lt;br&gt;
-(From Thread &amp;quot;[RT] Serving Apache Forrest site from live Forrest&amp;quot;&lt;br&gt;
-on dev-list. Will add link later.)</p>
-</div>
-<a name="N100F1"></a><a name="%5BFOR-343%5D+Upgrading+Plugins"></a>
-<h2 class="underlined_10">[FOR-343] Upgrading Plugins</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-343">http://issues.apache.org/jira/browse/FOR-343</a>
-</p>
-<p>Currently when installing a plugin Forrest attempts to install the most suitable version available. However, it makes no attempt to upgrade plugins when an upgrade becomes available.&lt;br&gt;
+
 &lt;br&gt;
-We need a traget in the buildfile that will upgrade an indicated plugin when possible. This can then (optionally) be used when running Forrest to automatically upgrade plugins.</p>
+However, we do have a sitemap transformer to &amp;quot;relativize&amp;quot; and &amp;quot;absolutize&amp;quot; the links. Should it always trim the leading slash? Or are there cases where that should not happen, so cannot generalise?</p>
 </div>
-<a name="N100FF"></a><a name="%5BFOR-284%5D+link+rewriting+broken+when+linking+to+xml+source+views+which+contain+site%3A+links"></a>
-<h2 class="underlined_10">[FOR-284] link rewriting broken when linking to xml source views which contain site: links</h2>
+<a name="N100FF"></a><a name="%5BFOR-705%5D+Target+of+LocationMap+rewriteDemo+causes+build+failure+when+target+not+available"></a>
+<h2 class="underlined_10">[FOR-705] Target of LocationMap rewriteDemo causes build failure when target not available</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-284">http://issues.apache.org/jira/browse/FOR-284</a>
+<a href="http://issues.apache.org/jira/browse/FOR-705">http://issues.apache.org/jira/browse/FOR-705</a>
 </p>
-<p>When linking to *.xml files (e.g. to demonstrate a source file) then if that file contains &amp;quot;site:&amp;quot; or &amp;quot;ext:&amp;quot; links, then they are reported as broken, e.g. docs/site:dtd-docs</p>
-</div>
-<a name="N1010D"></a><a name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
-<h2 class="underlined_10">[FOR-241] character entities (e.g. ampersand) are expanded again for href or src attributes</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-241">http://issues.apache.org/jira/browse/FOR-241</a>
-</p>
-<p>If I have a url like this inside the XML source:
-&lt;br&gt;
-
-&lt;br&gt;
-&lt;a href="http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;type=1"&gt;http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;amp;type=1&lt;/a&gt;
-&lt;br&gt;
-
-&lt;br&gt;
-validate-xdocs fails because it wants the literal &amp;amp; to be typed out as
-&lt;br&gt;
-&amp;amp; instead. So I correct it to become:
+<p>Build fails when given target URL of rewriteDemo is not available (site down, no longer exists, incorrect URL typing etc).
 &lt;br&gt;
 
 &lt;br&gt;
-&lt;a href="http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;type=1"&gt;http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;amp;type=1&lt;/a&gt;
+For various reasons given in [1] and [2] this default feature should remain but alternative options should be made available. Possible solutions given in [3]
 &lt;br&gt;
 
 &lt;br&gt;
-However, the generated HTML has the entity resolution UNDONE!:
+[1] &lt;a href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=112826350500282"&gt;http://marc.theaimsgroup.com/?l=forrest-dev&amp;amp;m=112826350500282&lt;/a&gt;
 &lt;br&gt;
 
 &lt;br&gt;
-&lt;a href="http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;type=1"&gt;http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;amp;type=1&lt;/a&gt;
+[2] &lt;a href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=11270994920771"&gt;http://marc.theaimsgroup.com/?l=forrest-dev&amp;amp;m=11270994920771&lt;/a&gt;
 &lt;br&gt;
 
 &lt;br&gt;
-This HTML fails validation as 4.01 transitional.
+[3] &lt;a href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=112859428219336&amp;w=2"&gt;http://marc.theaimsgroup.com/?l=forrest-dev&amp;amp;m=112859428219336&amp;amp;w=2&lt;/a&gt;
 &lt;br&gt;
 
 &lt;br&gt;
-David Crossley adds:
-&lt;br&gt;
-There is a demonstration of the problem in the document
-&lt;br&gt;
-src/documentation/content/xdocs/docs/dreams.xml
-&lt;br&gt;
-The ampersand in the link element text is properly handled but
-&lt;br&gt;
-the ampersand in the link href attribute is not.</p>
+</p>
 </div>
-<a name="N1011B"></a><a name="%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs"></a>
-<h2 class="underlined_10">[FOR-209] First level selected tab is not highlighted when containing 2nd level tabs</h2>
+<a name="N1010D"></a><a name="%5BFOR-721%5D+entries+without+labels+in+site.xml+are+now+being+crawled+and+generated"></a>
+<h2 class="underlined_10">[FOR-721] entries without labels in site.xml are now being crawled and generated</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-209">http://issues.apache.org/jira/browse/FOR-209</a>
+<a href="http://issues.apache.org/jira/browse/FOR-721">http://issues.apache.org/jira/browse/FOR-721</a>
 </p>
-<p>When there are two levels of tabs, the selected first level tab does not get highlighted, nor are there any other visual or structural clues as to which first-level tab is active, and which contains the displayed 2nd level tabs.
+<p>In our forrest/site-author/content/xdocs/site.xml there are two entries without &amp;quot;label&amp;quot; attributes. Previously these documents were not being generated. Not sure if this change in behaviour is good or bad. Needs investigation.
 &lt;br&gt;
 
 &lt;br&gt;
-This is checked with both the default skin, and with tigris-style.
-&lt;br&gt;
-</p>
+This is most likely a side-effect of the workaround for issue FOR-675</p>
 </div>
-<a name="N10129"></a><a name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
-<h2 class="underlined_10">[FOR-211] whole-site html and pdf: broken ext links</h2>
+<a name="N1011B"></a><a name="%5BFOR-699%5D+Beginner+HowTos+for+installing+Forrest"></a>
+<h2 class="underlined_10">[FOR-699] Beginner HowTos for installing Forrest</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-211">http://issues.apache.org/jira/browse/FOR-211</a>
+<a href="http://issues.apache.org/jira/browse/FOR-699">http://issues.apache.org/jira/browse/FOR-699</a>
 </p>
-<p>In the the generated site.html all of the external links are broken (i.e. the href attributes are like ... error:#ext:forrest).</p>
+<p>These are a whole group of HowTos that I wrote for my local users (probably a tutorial would be a better format).  They are not complete, nor tidied at this point, but they cover a lot of basic step-by-step stuff specifically geared towards Linux with Gnome desktop and Windows XP.  Figured I would put them out there so we can pull out bits we may want to use.</p>
 </div>
-<a name="N10137"></a><a name="%5BFOR-215%5D+site.lucene+name+colaps+with+site.html+request"></a>
-<h2 class="underlined_10">[FOR-215] site.lucene name colaps with site.html request</h2>
+<a name="N10129"></a><a name="%5BFOR-644%5D+whitespace+cleanup"></a>
+<h2 class="underlined_10">[FOR-644] whitespace cleanup</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-215">http://issues.apache.org/jira/browse/FOR-215</a>
+<a href="http://issues.apache.org/jira/browse/FOR-644">http://issues.apache.org/jira/browse/FOR-644</a>
 </p>
-<p>Any link called site.html or site.pdf produce a loop on the search funcionality.&lt;br&gt;
-&lt;br&gt;
-The reason is an internal request called &lt;a href="cocoon://site.lucene"&gt;cocoon://site.lucene&lt;/a&gt; a work around would be to choose another name for this internal request.&lt;br&gt;
-&lt;br&gt;
-But this means that a request called /index-creation.html would have the same problem.&lt;br&gt;
+<p>We have much inconsistent whitespace in all of our files. This is known to cause trouble in a collaborative environment. See discussion at: &lt;a href="http://marc.theaimsgroup.com/?t=112450901100001"&gt;http://marc.theaimsgroup.com/?t=112450901100001&lt;/a&gt; and see the list at trunk/etc/whitespace-cleanup.txt
 &lt;br&gt;
+
 &lt;br&gt;
+This Issue will be used to announce which section of the repository is due to be cleaned next. Please keep discussion on that mail thread.</p>
+</div>
+<a name="N10137"></a><a name="%5BFOR-645%5D+patches+for+whitespace+cleanup"></a>
+<h2 class="underlined_10">[FOR-645] patches for whitespace cleanup</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-645">http://issues.apache.org/jira/browse/FOR-645</a>
 </p>
+<p>Use this issue to provide patches for the whitespace cleanup.</p>
 </div>
-<a name="N10145"></a><a name="%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately"></a>
-<h2 class="underlined_10">[FOR-203] 2nd level tabs are not selected appropriately</h2>
+<a name="N10145"></a><a name="%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links"></a>
+<h2 class="underlined_10">[FOR-210] whole-site html and pdf: broken link faq, broken image links</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-203">http://issues.apache.org/jira/browse/FOR-203</a>
+<a href="http://issues.apache.org/jira/browse/FOR-210">http://issues.apache.org/jira/browse/FOR-210</a>
 </p>
-<p>The 2nd level tabs are not shown for menu entries that caused the issue FOR-111. This happens because the starts-with() path comparison fails for menu entries that do not reside the same directory as is specified in the &amp;quot;dir&amp;quot; attribute of the 2nd level tabs.
-&lt;br&gt;
-
-&lt;br&gt;
-See the attached bug-demo.tgz for an example. Select &amp;quot;Samples/Apache document&amp;quot; and notice that the 2nd level tabs are shown. Now select &amp;quot;Samples/BUG DEMO&amp;quot; and notice that the 2nd level tabs are not shown.
-&lt;br&gt;
-
+<p>The &amp;quot;fresh-site&amp;quot; build from 'forrest seed site' reports some failures for faq.html and various missing images. Wonder if sitemap issue?&lt;br&gt;
 &lt;br&gt;
-This is because the document corresponding to &amp;quot;Samples/Apache document&amp;quot; resides in the directory &amp;quot;/samples&amp;quot; whereas the document corresponding to &amp;quot;Samples/BUG DEMO&amp;quot; resides in the directory &amp;quot;/bug-sample&amp;quot;.
-&lt;br&gt;
-
-&lt;br&gt;
-Kind regards,
-&lt;br&gt;
-&amp;nbsp;&amp;nbsp;Lorenz Froihofer.</p>
+</p>
 </div>
-<a name="N10153"></a><a name="%5BFOR-184%5D+Switch+to+XHTML2"></a>
-<h2 class="underlined_10">[FOR-184] Switch to XHTML2</h2>
+<a name="N10153"></a><a name="%5BFOR-200%5D+Locationmap+for+Forrest+and+Users"></a>
+<h2 class="underlined_10">[FOR-200] Locationmap for Forrest and Users</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-184">http://issues.apache.org/jira/browse/FOR-184</a>
+<a href="http://issues.apache.org/jira/browse/FOR-200">http://issues.apache.org/jira/browse/FOR-200</a>
 </p>
-<p>Switch to using XHTML2 as a base and intermediate format. This means also using RelaxNG validations, new sitemap pipelines, new stylesheets, new input/output for &amp;quot;views&amp;quot;. See the steps in thread: &lt;a href="http://marc.theaimsgroup.com/?t=112512735800002"&gt;http://marc.theaimsgroup.com/?t=112512735800002&lt;/a&gt;</p>
+<p>The locationmap gives us the ability to specify where sources are, both for Forrest and for the users.
+&lt;br&gt;
+
+&lt;br&gt;
+Beware that it will not work for raw files that are not linked, as this &amp;quot;feature&amp;quot; currently uses a fixed dir being being copied by Ant.</p>
 </div>
-<a name="N10161"></a><a name="%5BFOR-187%5D+Redefine+project+documentation+dirs"></a>
-<h2 class="underlined_10">[FOR-187] Redefine project documentation dirs</h2>
+<a name="N10161"></a><a name="%5BFOR-726%5D+use+locationmap+in+all+of+the+plugins"></a>
+<h2 class="underlined_10">[FOR-726] use locationmap in all of the plugins</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-187">http://issues.apache.org/jira/browse/FOR-187</a>
+<a href="http://issues.apache.org/jira/browse/FOR-726">http://issues.apache.org/jira/browse/FOR-726</a>
 </p>
-<p>We should finalize all discussions about where to put sources and extensions in the projects.</p>
+<p>Each plugin has sitemaps that need to use the locationmap.
+&lt;br&gt;
+
+&lt;br&gt;
+(Perhaps we need Jira sub-tasks for each plugin.)</p>
 </div>
 </div>
 <!--+

Modified: forrest/site/forrest-issues.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-issues.pdf?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/guidelines.html
URL: http://svn.apache.org/viewcvs/forrest/site/guidelines.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/guidelines.html (original)
+++ forrest/site/guidelines.html Sun Dec 18 17:31:25 2005
@@ -957,6 +957,9 @@
 
 <!-- FIXME:
 
+The default is lazy consensus. So just get on with the job
+unless someone asks to stop, review, perhaps revert.
+
 ==================
 > We should make mention somewhere of our relationship to other projects
 > Cocoon committers are Forrest committers; something with xml-commons

Modified: forrest/site/index.html
URL: http://svn.apache.org/viewcvs/forrest/site/index.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/index.html (original)
+++ forrest/site/index.html Sun Dec 18 17:31:25 2005
@@ -239,7 +239,7 @@
 <ul>
         
 <li>
-<strong>Step 1</strong>: Do <span class="codefrag ">'forrest seed'</span> to populate
+<strong>Step 1</strong>: Do <span class="codefrag">'forrest seed'</span> to populate
           the directory with template site structure and contents.</li>
         
 <li>
@@ -247,9 +247,9 @@
           task-specific, presentation-neutral XML.</li>
         
 <li>
-<strong>Step 3</strong>: Do <span class="codefrag ">'forrest run'</span> then use
+<strong>Step 3</strong>: Do <span class="codefrag">'forrest run'</span> then use
           the web browser to immediately review
-          changes at <span class="codefrag ">http://localhost:8888/</span>
+          changes at <span class="codefrag">http://localhost:8888/</span>
           
 <ul>
 <li>
@@ -267,7 +267,7 @@
 </li>
         
 <li>
-<strong>Step 4</strong>: Do <span class="codefrag ">'forrest'</span> to generate the
+<strong>Step 4</strong>: Do <span class="codefrag">'forrest'</span> to generate the
           complete website from the XML sources.
           Various styles (known as skins) are available. Custom skins
           can be developed.</li>

Added: forrest/site/locationmap.xml
URL: http://svn.apache.org/viewcvs/forrest/site/locationmap.xml?rev=357603&view=auto
==============================================================================
--- forrest/site/locationmap.xml (added)
+++ forrest/site/locationmap.xml Sun Dec 18 17:31:25 2005
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+  Copyright 2005 The Apache Software Foundation or its licensors,
+  as applicable.
+
+  Licensed under the Apache License, Version 2.0 (the "License");
+  you may not use this file except in compliance with the License.
+  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+
+<!-- Default Forrest locationmap for issues related files -->
+
+<locationmap xmlns="http://apache.org/forrest/locationmap/1.0">
+
+  <components>
+    <matchers default="lm">
+      <matcher 
+        name="lm" 
+        src="org.apache.forrest.locationmap.WildcardLocationMapHintMatcher"/>
+    </matchers>
+    <selectors default="exists">
+          <selector name="exists" logger="sitemap.selector.exists"  
+                    src="org.apache.forrest.sourceexists.SourceExistsSelector" />
+    </selectors>
+  </components>
+  
+  <locator>
+  
+    <match pattern="forrest.issues-rss-url">
+        <location src="{forrest:issues-rss-url}" />
+    </match>
+    
+  </locator>
+</locationmap>

Propchange: forrest/site/locationmap.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: forrest/site/mirrors.html
URL: http://svn.apache.org/viewcvs/forrest/site/mirrors.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/mirrors.html (original)
+++ forrest/site/mirrors.html Sun Dec 18 17:31:25 2005
@@ -199,7 +199,7 @@
 <div class="section">
 <p class="note">Please realise that Forrest is still pre-1.0 release version. It is certainly usable for those who are prepared to move with it. See more notes about <a href="index.html#status">status</a>.</p>
 <p>Use the links below to download a distribution of Apache Forrest from one of our mirrors. It is good practice to <a href="[location]#verify">verify the integrity</a> of the distribution files.</p>
-<p>Apache Forrest is distributed as a <span class="codefrag ">zip</span> archive (for Windows) and as a <span class="codefrag ">tar.gz</span> archive (for UNIX). The contents are the same, the only difference is the line-endings of all text files.</p>
+<p>Apache Forrest is distributed as a <span class="codefrag">zip</span> archive (for Windows) and as a <span class="codefrag">tar.gz</span> archive (for UNIX). The contents are the same, the only difference is the line-endings of all text files.</p>
 <p>The distribution contains all of the source code, documentation, and resources, together with the pre-built ready-to-run forrest binary.</p>
 </div>
 <a name="N1002C"></a><a name="closest"></a>
@@ -235,7 +235,7 @@
 <h2 class="underlined_10">Verify releases</h2>
 <div class="section">
 <p>It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.</p>
-<p>The PGP signatures can be verified using <a href="http://www.pgpi.org/">PGP</a> or <a href="http://www.gnupg.org/">GPG</a>. First download the Apache Forrest <a href="http://svn.apache.org/repos/asf/forrest/trunk/KEYS">KEYS</a> as well as the <span class="codefrag ">asc</span> signature file for the particular distribution. It is important that you get these files from the ultimate trusted source - the main ASF distribution site, rather than from a mirror. Then verify the signatures using ...</p>
+<p>The PGP signatures can be verified using <a href="http://www.pgpi.org/">PGP</a> or <a href="http://www.gnupg.org/">GPG</a>. First download the Apache Forrest <a href="http://svn.apache.org/repos/asf/forrest/trunk/KEYS">KEYS</a> as well as the <span class="codefrag">asc</span> signature file for the particular distribution. It is important that you get these files from the ultimate trusted source - the main ASF distribution site, rather than from a mirror. Then verify the signatures using ...</p>
 <pre>% pgpk -a KEYS
 % pgpv apache-forrest-X.Y.tar.gz.asc
 
@@ -249,7 +249,7 @@
 % gpg --import KEYS
 % gpg --verify apache-forrest-X.Y.tar.gz.asc
 </pre>
-<p>To verify the MD5 signature on the files, you need to use a program called <span class="codefrag ">md5</span> or <span class="codefrag ">md5sum</span>, which is included in many unix distributions. It is also available as part of <a href="http://www.gnu.org/software/textutils/textutils.html">GNU Textutils</a>. Windows users can get binary md5 programs from <a href="http://www.fourmilab.ch/md5/">here</a>, <a href="http://www.pc-tools.net/win32/freeware/console/">here</a>, or <a href="http://www.slavasoft.com/fsum/">here</a>.</p>
+<p>To verify the MD5 signature on the files, you need to use a program called <span class="codefrag">md5</span> or <span class="codefrag">md5sum</span>, which is included in many unix distributions. It is also available as part of <a href="http://www.gnu.org/software/textutils/textutils.html">GNU Textutils</a>. Windows users can get binary md5 programs from <a href="http://www.fourmilab.ch/md5/">here</a>, <a href="http://www.pc-tools.net/win32/freeware/console/">here</a>, or <a href="http://www.slavasoft.com/fsum/">here</a>.</p>
 <p>We strongly recommend you verify your downloads with both PGP and MD5.</p>
 </div>
 </div>

Modified: forrest/site/pluginDocs/plugins_0_70/index.html
URL: http://svn.apache.org/viewcvs/forrest/site/pluginDocs/plugins_0_70/index.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/pluginDocs/plugins_0_70/index.html (original)
+++ forrest/site/pluginDocs/plugins_0_70/index.html Sun Dec 18 17:31:25 2005
@@ -199,8 +199,8 @@
             Plugins are a way of extending Forrest to
             satisfy site-specific needs. If a site requires one or 
             more plugins then the site designer will 
-            have named them in the <span class="codefrag ">project.required.plugins</span> property 
-            in the projects <span class="codefrag ">forrest.properties</span> file. When Forrest 
+            have named them in the <span class="codefrag">project.required.plugins</span> property 
+            in the projects <span class="codefrag">forrest.properties</span> file. When Forrest 
             builds the site it will automatically discover the plugin and install 
             it.For more information on how to use plugins see
             <a href="http://forrest.apache.org/pluginDocs/plugins_0_70/usingPlugins.html">

Modified: forrest/site/pluginDocs/plugins_0_70/pluginInfrastructure.html
URL: http://svn.apache.org/viewcvs/forrest/site/pluginDocs/plugins_0_70/pluginInfrastructure.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/pluginDocs/plugins_0_70/pluginInfrastructure.html (original)
+++ forrest/site/pluginDocs/plugins_0_70/pluginInfrastructure.html Sun Dec 18 17:31:25 2005
@@ -225,8 +225,8 @@
       to suit individual projects needs.</p>
 <a name="N10023"></a><a name="pluginTypes"></a>
 <h3 class="underlined_5">Types of Plugin</h3>
-<p>There are three types of plugin, <span class="codefrag ">input</span>,
-        <span class="codefrag ">output</span> and <span class="codefrag ">internal</span>. Each plugin has a 
+<p>There are three types of plugin, <span class="codefrag">input</span>,
+        <span class="codefrag">output</span> and <span class="codefrag">internal</span>. Each plugin has a 
         specific role to play and extends a different part of Forrest:</p>
 <pre class="code">
                             internal plugins
@@ -242,22 +242,22 @@
                      (**.xml)         (**.html, **.pdf etc.) 
 </pre>
 <p>The name of the sitemap will reflect the type of plugin in use.
-        That is, an internal plugin will have a sitemap called <span class="codefrag ">internal.xmap</span>,
-        an output plugin has <span class="codefrag ">output.xmap</span> and an input plugin has
-        <span class="codefrag ">input.xmap</span>. In addition, an input plugin can optionally provide a
-        <span class="codefrag ">resources.xmap</span>.</p>
+        That is, an internal plugin will have a sitemap called <span class="codefrag">internal.xmap</span>,
+        an output plugin has <span class="codefrag">output.xmap</span> and an input plugin has
+        <span class="codefrag">input.xmap</span>. In addition, an input plugin can optionally provide a
+        <span class="codefrag">resources.xmap</span>.</p>
 <a name="N10048"></a><a name="inputPlugins"></a>
 <h4>Input Plugins</h4>
 <p>Input plugins provide a new source format. For example, the
           OpenOffice.org plugin extends Forrest to allow the use of
           OpenOffice.org Application file formats.</p>
-<p>An input plugin provides an <span class="codefrag ">input.xmap</span> file. 
+<p>An input plugin provides an <span class="codefrag">input.xmap</span> file. 
           This provides the source matchers (i.e. **.xml), it is 
           mounted in forrest.xmap before the default forrest **.xml behaviour 
           and therefore can override that default behaviour but it will not 
           interfere with any internal Forrest infrastructure matches, or any 
           other plugins infrastructure matches.</p>
-<p>An input plugin may also provide a <span class="codefrag ">resources.xmap</span>
+<p>An input plugin may also provide a <span class="codefrag">resources.xmap</span>
           file. This can be used to match additional resources that are not 
           stored in XML files, for example, javascript files.</p>
 <a name="N1005E"></a><a name="outputPlugins"></a>
@@ -265,7 +265,7 @@
 <p>Output plugins provide a new output format. For example, the
           s5 plugin extends Forrest to produce HTML slides from Forrest
           documents.</p>
-<p>An output plugin provides an <span class="codefrag ">output.xmap</span> file.
+<p>An output plugin provides an <span class="codefrag">output.xmap</span> file.
           This provides the relevant output matchers (i.e. 
           **.html, **.pdf, **.slides), it is mounted before any of the default 
           matchers for Forrest and so can override this default behaviour.</p>
@@ -276,7 +276,7 @@
           internal operations. For example, the IMSManifest plugin
           allows Forrest projects to use an IMS Manifest file instead of 
           a site.xml and tabs.xml configuration files.</p>
-<p>Internal plugins provide an <span class="codefrag ">internal.xmap</span> file. 
+<p>Internal plugins provide an <span class="codefrag">internal.xmap</span> file. 
           This provides the infrastructure matchers (i.e. 
           site.xml, faq.xml, issues.xml), and will be mounted before 
           *any* of the Forrest matches. This sitemap can override any behaviour 
@@ -296,8 +296,8 @@
         include a relevant reverse domain name. For example:</p>
 <pre class="code">org.apache.forrest.plugin.PLUGIN_TYPE.PLUGIN_NAME</pre>
 <pre class="code">net.sf.forrestPlugins.PLUGIN_TYPE.PLUGIN_NAME</pre>
-<p>Where <span class="codefrag ">PLUGIN_TYPE</span> is either "internal", "input" or
-        "output" and <span class="codefrag ">PLUGIN_NAME"</span> is a suitable name chosen by
+<p>Where <span class="codefrag">PLUGIN_TYPE</span> is either "internal", "input" or
+        "output" and <span class="codefrag">PLUGIN_NAME"</span> is a suitable name chosen by
         yourself.</p>
 <div class="warning">
 <div class="label">Warning</div>
@@ -403,8 +403,8 @@
 <h2 class="underlined_10">How does Installation work?</h2>
 <div class="section">
 <p>When Forrest installs a plugin it downloads a zip of the plugin code and 
-    extracts it into the <span class="codefrag ">plugins</span> directory of Forrest and an entry is made 
-    in <span class="codefrag ">src/plugins/[input|internal|output].xmap</span> (recall the actual sitemap
+    extracts it into the <span class="codefrag">plugins</span> directory of Forrest and an entry is made 
+    in <span class="codefrag">src/plugins/[input|internal|output].xmap</span> (recall the actual sitemap
     name is dependant on the type of plugin it belongs to. For example, installing the 
     IMSManifest plugin described above will result in the following entry 
     being added to the plugin sitemap:</p>

Modified: forrest/site/pluginDocs/plugins_0_70/usingPlugins.html
URL: http://svn.apache.org/viewcvs/forrest/site/pluginDocs/plugins_0_70/usingPlugins.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/pluginDocs/plugins_0_70/usingPlugins.html (original)
+++ forrest/site/pluginDocs/plugins_0_70/usingPlugins.html Sun Dec 18 17:31:25 2005
@@ -192,7 +192,7 @@
       plugin mechanism.</p>
 <a name="N10016"></a><a name="What+plugins+are+available%3F"></a>
 <h3 class="underlined_5">What plugins are available?</h3>
-<p>You can run the command <span class="codefrag ">forrest available-plugins</span> to get
+<p>You can run the command <span class="codefrag">forrest available-plugins</span> to get
         a list of the known plugins for Forrest.</p>
 <p>If you would like to have your own plugin added to this list then
         contact the <a href="../../mail-lists.html">developer mailing list</a>.</p>
@@ -203,11 +203,11 @@
 <h2 class="underlined_10">How is a Plugin Installed?</h2>
 <div class="section">
 <p>If a site requires one or more plugins then the site designer will 
-      have named them in the <span class="codefrag ">project.required.plugins</span> property 
-      in the projects <span class="codefrag ">forrest.properties</span> file. When Forrest 
+      have named them in the <span class="codefrag">project.required.plugins</span> property 
+      in the projects <span class="codefrag">forrest.properties</span> file. When Forrest 
       builds the site it will automatically discover the plugin and install 
       it. In otherwords, the user need do nothing. For example, 
-      <span class="codefrag ">project.required.plugins=org.apache.forrest.plugin.input.OpenOffice.org,org.apache.forrest.plugin.input.simplifiedDocbook</span>
+      <span class="codefrag">project.required.plugins=org.apache.forrest.plugin.input.OpenOffice.org,org.apache.forrest.plugin.input.simplifiedDocbook</span>
       will cause Forrest to load the plugins called "org.apache.forrest.plugin.input.OpenOffice.org" and
       "org.apache.forrest.plugin.input.simplifiedDocbook".</p>
 <p>In the absence of a version number for the plugin (as is the case in the examples above)
@@ -216,7 +216,7 @@
       is incompatible with your current site. To force Forrest into using a specific version of 
       a plugin you shuld add "-VERSION_NUMBER" to the end of the plugin name. For example,
       to force forrest to use the 1.0 version of the OpenOffice.org plugin you would use
-      <span class="codefrag ">org.apache.forrest.plugin.input.OpenOffice.org-1.0</span> If you define a version of the
+      <span class="codefrag">org.apache.forrest.plugin.input.OpenOffice.org-1.0</span> If you define a version of the
       plugin that does not exist then it will fall back to using the most recent version avialable.
       This feature is useful when 
       developing a new site as you can quickly force a plugin upgrade by deleting all installed 
@@ -231,25 +231,25 @@
         At this time some of the functionality previously in Forrest was
         extracted into a plugin. However, we have not broken backward 
         compatability with earlier versions. In the absence of a
-        <span class="codefrag ">project.required.plugins</span> property in the projects 
-        <span class="codefrag ">forrest.properties</span> file all plugins that contain 
+        <span class="codefrag">project.required.plugins</span> property in the projects 
+        <span class="codefrag">forrest.properties</span> file all plugins that contain 
         functionality previously part of Forrest itself will be loaded
         automatically. Unless you intend to use new functionality provided
         by a plugin you will not need to make any changes top your project.</p>
 <p>If you do require additional plugin functionality, be sure to
         include all required plugins in the 
-        <span class="codefrag ">project.required.plugins</span> property in the project's
-        <span class="codefrag ">forrest.properties</span>. You can view
-        <span class="codefrag ">main/webapp/default-forrest.properties</span>
+        <span class="codefrag">project.required.plugins</span> property in the project's
+        <span class="codefrag">forrest.properties</span>. You can view
+        <span class="codefrag">main/webapp/default-forrest.properties</span>
         to see the names of plugins that provide previously core 
         functionality.</p>
 <p>It is also worth noting that there is a small performance 
         improvement if you remove plugins that are not in use. Therefore,
         if you do not use one or more of the plugins named in the 
-        <span class="codefrag ">project.required.plugins</span> property of 
-        <span class="codefrag ">main/webapp/default-forrest.properties</span>
+        <span class="codefrag">project.required.plugins</span> property of 
+        <span class="codefrag">main/webapp/default-forrest.properties</span>
         it is recomended that you override this value in your project's
-        <span class="codefrag ">forrest.properties</span> file.</p>
+        <span class="codefrag">forrest.properties</span> file.</p>
 </div>
     
     
@@ -260,7 +260,7 @@
       and full docbook plugins may try and process the same files. In this 
       instance the one that is mounted first will take precedence. Plugins 
       are mounted in the order they appear in the 
-      <span class="codefrag ">project.required.plugins</span> property, therefore the mounting 
+      <span class="codefrag">project.required.plugins</span> property, therefore the mounting 
       order and therefore processing precedence is under user control.</p>
 </div>
     

Modified: forrest/site/pluginDocs/plugins_0_80/index.html
URL: http://svn.apache.org/viewcvs/forrest/site/pluginDocs/plugins_0_80/index.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/index.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/index.html Sun Dec 18 17:31:25 2005
@@ -199,8 +199,8 @@
             Plugins are a way of extending Forrest to
             satisfy site-specific needs. If a site requires one or 
             more plugins then the site designer will 
-            have named them in the <span class="codefrag ">project.required.plugins</span> property 
-            in the projects <span class="codefrag ">forrest.properties</span> file. When Forrest 
+            have named them in the <span class="codefrag">project.required.plugins</span> property 
+            in the projects <span class="codefrag">forrest.properties</span> file. When Forrest 
             builds the site it will automatically discover the plugin and install 
             it.For more information on how to use plugins see
             <a href="http://forrest.apache.org/pluginDocs/plugins_0_70/usingPlugins.html">

Modified: forrest/site/pluginDocs/plugins_0_80/pluginInfrastructure.html
URL: http://svn.apache.org/viewcvs/forrest/site/pluginDocs/plugins_0_80/pluginInfrastructure.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/pluginInfrastructure.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/pluginInfrastructure.html Sun Dec 18 17:31:25 2005
@@ -225,8 +225,8 @@
       to suit individual projects needs.</p>
 <a name="N10023"></a><a name="pluginTypes"></a>
 <h3 class="underlined_5">Types of Plugin</h3>
-<p>There are three types of plugin, <span class="codefrag ">input</span>,
-        <span class="codefrag ">output</span> and <span class="codefrag ">internal</span>. Each plugin has a 
+<p>There are three types of plugin, <span class="codefrag">input</span>,
+        <span class="codefrag">output</span> and <span class="codefrag">internal</span>. Each plugin has a 
         specific role to play and extends a different part of Forrest:</p>
 <pre class="code">
                             internal plugins
@@ -246,13 +246,13 @@
 <p>Input plugins provide a new source format. For example, the
           OpenOffice.org plugin extends Forrest to allow the use of
           OpenOffice.org Application file formats.</p>
-<p>An input plugin provides an <span class="codefrag ">input.xmap</span> file. 
+<p>An input plugin provides an <span class="codefrag">input.xmap</span> file. 
           This provides the source matchers (i.e. **.xml), it is 
           mounted in forrest.xmap before the default forrest **.xml behaviour 
           and therefore can override that default behaviour but it will not 
           interfere with any internal Forrest infrastructure matches, or any 
           other plugins infrastructure matches.</p>
-<p>An input plugin may also provide a <span class="codefrag ">resources.xmap</span>
+<p>An input plugin may also provide a <span class="codefrag">resources.xmap</span>
           file. This can be used to match additional resources that are not 
           stored in XML files, for example, javascript files.</p>
 <a name="N1004F"></a><a name="outputPlugins"></a>
@@ -260,7 +260,7 @@
 <p>Output plugins provide a new output format. For example, the
           s5 plugin extends Forrest to produce HTML slides from Forrest
           documents.</p>
-<p>An output plugin provides an <span class="codefrag ">output.xmap</span> file.
+<p>An output plugin provides an <span class="codefrag">output.xmap</span> file.
           This provides the relevant output matchers (i.e. 
           **.html, **.pdf, **.slides), it is mounted before any of the default 
           matchers for Forrest and so can override this default behaviour.</p>
@@ -271,7 +271,7 @@
           internal operations. For example, the IMSManifest plugin
           allows Forrest projects to use an IMS Manifest file instead of 
           a site.xml and tabs.xml configuration files.</p>
-<p>Internal plugins provide an <span class="codefrag ">internal.xmap</span> file. 
+<p>Internal plugins provide an <span class="codefrag">internal.xmap</span> file. 
           This provides the infrastructure matchers (i.e. 
           site.xml, faq.xml, issues.xml), and will be mounted before 
           *any* of the Forrest matches. This sitemap can override any behaviour 
@@ -291,8 +291,8 @@
         include a relevant reverse domain name. For example:</p>
 <pre class="code">org.apache.forrest.plugin.PLUGIN_TYPE.PLUGIN_NAME</pre>
 <pre class="code">net.sf.forrestPlugins.PLUGIN_TYPE.PLUGIN_NAME</pre>
-<p>Where <span class="codefrag ">PLUGIN_TYPE</span> is either "internal", "input" or
-        "output" and <span class="codefrag ">PLUGIN_NAME"</span> is a suitable name chosen by
+<p>Where <span class="codefrag">PLUGIN_TYPE</span> is either "internal", "input" or
+        "output" and <span class="codefrag">PLUGIN_NAME"</span> is a suitable name chosen by
         yourself.</p>
 <div class="warning">
 <div class="label">Warning</div>
@@ -402,8 +402,8 @@
 <h2 class="underlined_10">How does Installation work?</h2>
 <div class="section">
 <p>When Forrest installs a plugin it downloads a zip of the plugin code and 
-    extracts it into the <span class="codefrag ">plugins</span> directory of Forrest and an entry is made 
-    in <span class="codefrag ">src/plugins/sitemap.xmap</span>. For example, installing the 
+    extracts it into the <span class="codefrag">plugins</span> directory of Forrest and an entry is made 
+    in <span class="codefrag">src/plugins/sitemap.xmap</span>. For example, installing the 
     IMSManifest plugin described above will result in the following entry 
     being added to the plugin sitemap:</p>
 <pre class="code">



Mime
View raw message