Return-Path: 
 <svn-return-5750-apmail-forrest-svn-archive=forrest.apache.org@forrest.apache.org>
Delivered-To: apmail-forrest-svn-archive@www.apache.org
Received: (qmail 76305 invoked from network); 10 Jun 2006 08:12:07 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 10 Jun 2006 08:12:07 -0000
Received: (qmail 74977 invoked by uid 500); 10 Jun 2006 08:12:06 -0000
Delivered-To: apmail-forrest-svn-archive@forrest.apache.org
Received: (qmail 74791 invoked by uid 500); 10 Jun 2006 08:12:05 -0000
Mailing-List: contact svn-help@forrest.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:svn-help@forrest.apache.org>
list-unsubscribe: <mailto:svn-unsubscribe@forrest.apache.org>
List-Post: <mailto:svn@forrest.apache.org>
Reply-To: "Forrest Developers List" <dev@forrest.apache.org>
List-Id: <svn.forrest.apache.org>
Delivered-To: mailing list svn@forrest.apache.org
Received: (qmail 74739 invoked by uid 99); 10 Jun 2006 08:12:04 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Jun 2006 01:12:04 -0700
X-ASF-Spam-Status: No, hits=-9.4 required=10.0
	tests=ALL_TRUSTED,NO_REAL_NAME
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [140.211.166.113] (HELO eris.apache.org) (140.211.166.113)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Jun 2006 01:12:01 -0700
Received: by eris.apache.org (Postfix, from userid 65534)
	id AEDAC1A9866; Sat, 10 Jun 2006 01:11:16 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r413268 [11/11] - in /forrest/site: ./ docs_0_60/
 docs_0_70/
 docs_0_80/
Date: Sat, 10 Jun 2006 08:11:11 -0000
To: svn@forrest.apache.org
From: crossley@apache.org
X-Mailer: svnmailer-1.0.8
Message-Id: <20060610081116.AEDAC1A9866@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Modified: forrest/site/docs_0_80/faq.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/faq.html?rev=413268&r1=413267&r2=413268&view=diff
==============================================================================
--- forrest/site/docs_0_80/faq.html (original)
+++ forrest/site/docs_0_80/faq.html Sat Jun 10 01:11:09 2006
@@ -442,7 +442,7 @@
 <a href="#i18n">2.18. How can I internationalise (i18n) my content?</a>
 </li>
 <li>
-<a href="#rawTML">2.19. How can I include HTML content that is not to be skinned by Forrest?</a>
+<a href="#rawHTML">2.19. How can I include HTML content that is not to be skinned by Forrest?</a>
 </li>
 <li>
 <a href="#javascript">2.20. How to include additional Javascript and CSS files?</a>
@@ -1129,10 +1129,10 @@
         by the <a href="http://cocoon.apache.org/2.1/userdocs/i18nTransformer.html">Cocoon i18n 
         Transformer</a>. You can see an example of how it works in the above linked issue.</p>
 </div>
-<a name="N102BD"></a><a name="rawTML"></a>
+<a name="N102BD"></a><a name="rawHTML"></a>
 <h4 class="faq">2.19. How can I include HTML content that is not to be skinned by Forrest?</h4>
 <div align="right">
-<a href="#rawTML-menu">^</a>
+<a href="#rawHTML-menu">^</a>
 </div>
 <div style="margin-left: 15px">
 <p>To serve, for example a legacy HTML site, add something like the following 
@@ -1165,12 +1165,12 @@
 <li>forrest</li>
           
 <li>
-<a href="http://localhost:8888/samples/linking.html#no-decoration">Read the doc</a>
+<span class="codefrag">http://localhost:8888/samples/linking.html#no-decoration</span>
 </li>
         
 </ol>
 </div>
-<a name="N102E3"></a><a name="javascript"></a>
+<a name="N102E2"></a><a name="javascript"></a>
 <h4 class="faq">2.20. How to include additional Javascript and CSS files?</h4>
 <div align="right">
 <a href="#javascript-menu">^</a>
@@ -1194,9 +1194,9 @@
           &lt;map:resource name="skin-read"&gt; section.
         </p>
 </div>
-<a name="N102F1"></a><a name="technical"></a>
+<a name="N102F0"></a><a name="technical"></a>
 <h3 class="underlined_5">3. Technical</h3>
-<a name="N102F5"></a><a name="java-code"></a>
+<a name="N102F4"></a><a name="java-code"></a>
 <h4 class="faq">3.1. Where is the Java code?</h4>
 <div align="right">
 <a href="#java-code-menu">^</a>
@@ -1219,7 +1219,7 @@
           with specialised purpose, e.g. PhotoGallery.
         </p>
 </div>
-<a name="N10303"></a><a name="populate-cache"></a>
+<a name="N10302"></a><a name="populate-cache"></a>
 <h4 class="faq">3.2. How to enhance the responsiveness of the cache?</h4>
 <div align="right">
 <a href="#populate-cache-menu">^</a>
@@ -1245,7 +1245,7 @@
 <p>Responsiveness can be further enhanced by utilising a transparent proxy server, e.g. Apache HTTP Server as a frontend. See <a href="http://wiki.apache.org/cocoon/ApacheModProxy">CocoonAndApacheModProxy</a>.
         </p>
 </div>
-<a name="N1031D"></a><a name="proxy_config"></a>
+<a name="N1031C"></a><a name="proxy_config"></a>
 <h4 class="faq">3.3. I'm behind a proxy and it's preventing Plugins from being downloaded, what should I
         do?</h4>
 <div align="right">
@@ -1261,7 +1261,7 @@
         To avoid to edit every project <span class="codefrag">forrest.properties</span> files, you can do once in your <span class="codefrag">${user.home}/forrest.properties</span> !</div>
 </div>
 </div>
-<a name="N10341"></a><a name="CVS_revison_tags"></a>
+<a name="N10340"></a><a name="CVS_revison_tags"></a>
 <h4 class="faq">3.4. How can I generate html-pages to show the revision tag of cvs?</h4>
 <div align="right">
 <a href="#CVS_revison_tags-menu">^</a>
@@ -1274,7 +1274,7 @@
 <p>This technique could also be used for a modification date with $Date: 2004/01/15 08:52:47
           $</p>
 </div>
-<a name="N10353"></a><a name="cli-xconf"></a>
+<a name="N10352"></a><a name="cli-xconf"></a>
 <h4 class="faq">3.5.  How to control the processing of URIs by Cocoon, e.g. exclude certain URIs, include
         other additional ones. </h4>
 <div align="right">
@@ -1312,7 +1312,7 @@
           <strong>foo/**</strong> to match that. </div>
 </div>
 </div>
-<a name="N10390"></a><a name="ignoring_javadocs"></a>
+<a name="N1038F"></a><a name="ignoring_javadocs"></a>
 <h4 class="faq">3.6.  How do I stop Forrest breaking on links to external files that may not exist, like
         javadocs? </h4>
 <div align="right">
@@ -1323,7 +1323,7 @@
             <span class="codefrag">cli.xconf</span>
           </a> Cocoon config file, and defining patterns for URLs to exclude. </p>
 </div>
-<a name="N1039F"></a><a name="claimed_patterns"></a>
+<a name="N1039E"></a><a name="claimed_patterns"></a>
 <h4 class="faq">3.7. Some of my files are not being processed because they use common filenames. </h4>
 <div align="right">
 <a href="#claimed_patterns-menu">^</a>
@@ -1339,7 +1339,7 @@
           with this issue (<a href="http://issues.apache.org/jira/browse/FOR-217">FOR-217</a>).
         </p>
 </div>
-<a name="N103B1"></a><a name="build_msg_a"></a>
+<a name="N103B0"></a><a name="build_msg_a"></a>
 <h4 class="faq">3.8. What do the symbols and numbers mean when Forrest lists each document that it has
         built? </h4>
 <div align="right">
@@ -1370,7 +1370,7 @@
         
 </ul>
 </div>
-<a name="N103CF"></a><a name="headless_operation"></a>
+<a name="N103CE"></a><a name="headless_operation"></a>
 <h4 class="faq">3.9.  When generating PNG images from SVG, I get an error: Can't connect to X11 window
         server using ':0.0' as the value of the DISPLAY variable. </h4>
 <div align="right">
@@ -1383,7 +1383,7 @@
 <pre class="code">forrest -Dforrest.jvmargs=-Djava.awt.headless=true site</pre>
 <p> See also <a href="http://cocoon.apache.org/2.1/faq/faq-configure-environment.html">Cocoon FAQ</a>. </p>
 </div>
-<a name="N103EB"></a><a name="project-logo-svg"></a>
+<a name="N103EA"></a><a name="project-logo-svg"></a>
 <h4 class="faq">3.10.  
         The project logo that is generated from SVG is truncating my project name.
       </h4>
@@ -1403,7 +1403,7 @@
           <a href="http://www.w3.org/Graphics/SVG/">SVG</a> resources.
         </p>
 </div>
-<a name="N10403"></a><a name="catalog"></a>
+<a name="N10402"></a><a name="catalog"></a>
 <h4 class="faq">3.11.  How do i configure my favourite XML editor or parser to find the local Forrest
         DTDs? </h4>
 <div align="right">
@@ -1413,7 +1413,7 @@
 <p> Notes are provided for various tools at <a href="../docs_0_80/catalog.html">Using Catalog Entity
             Resolver for local DTDs</a>. </p>
 </div>
-<a name="N1040F"></a><a name="skin"></a>
+<a name="N1040E"></a><a name="skin"></a>
 <h4 class="faq">3.12.  How to make the site look better and change its skin? </h4>
 <div align="right">
 <a href="#skin-menu">^</a>
@@ -1425,7 +1425,7 @@
 <p> See notes about <a href="../docs_0_80/howto/../your-project.html#skins">configuration</a> of the skins.
           Some projects may have special needs and can define their <a href="../docs_0_80/howto/../your-project.html#new_skin">own skin</a>. </p>
 </div>
-<a name="N10426"></a><a name="xsp"></a>
+<a name="N10425"></a><a name="xsp"></a>
 <h4 class="faq">3.13. How do I enable XSP processing?</h4>
 <div align="right">
 <a href="#xsp-menu">^</a>
@@ -1473,7 +1473,7 @@
 </ol>
 <p>See also the <a href="http://wiki.apache.org/cocoon/AddingXSPToForrest">AddingXSPToForrest</a> Wiki page.</p>
 </div>
-<a name="N10461"></a><a name="breadcrumbs"></a>
+<a name="N10460"></a><a name="breadcrumbs"></a>
 <h4 class="faq">3.14. How do breadcrumbs work? Why don't they work locally?</h4>
 <div align="right">
 <a href="#breadcrumbs-menu">^</a>
@@ -1492,7 +1492,7 @@
           are viewing the site locally, there is no domain and so there will be no extra
           breadcrumbs, only the ones that are specified in <span class="codefrag">skinconf.xml</span>. </p>
 </div>
-<a name="N10476"></a><a name="run_port"></a>
+<a name="N10475"></a><a name="run_port"></a>
 <h4 class="faq">3.15. How do I make forrest run listen on a different port?</h4>
 <div align="right">
 <a href="#run_port-menu">^</a>
@@ -1508,7 +1508,7 @@
         
 </p>
 </div>
-<a name="N1048A"></a><a name="debugging"></a>
+<a name="N10489"></a><a name="debugging"></a>
 <h4 class="faq">3.16. Can I run Forrest with Java debugging turned on?</h4>
 <div align="right">
 <a href="#debugging-menu">^</a>
@@ -1520,7 +1520,7 @@
         to the <span class="codefrag">forrest.jvmargs</span> property in the <span class="codefrag">forrest.properties</span>
         file. Don't forget to ensure the property is uncommented in that file.</p>
 </div>
-<a name="N1049B"></a><a name="checksums"></a>
+<a name="N1049A"></a><a name="checksums"></a>
 <h4 class="faq">3.17. How do I enable Cocoon's document checksum feature?</h4>
 <div align="right">
 <a href="#checksums-menu">^</a>
@@ -1554,9 +1554,9 @@
         installation-wide cli.xconf file.
         </p>
 </div>
-<a name="N104B7"></a><a name="old_faqs"></a>
+<a name="N104B6"></a><a name="old_faqs"></a>
 <h3 class="underlined_5">4. Older version: 0.6</h3>
-<a name="N104BB"></a><a name="old_claimed_patterns"></a>
+<a name="N104BA"></a><a name="old_claimed_patterns"></a>
 <h4 class="faq">4.1. Some of my files are not being processed because they use common filenames. </h4>
 <div align="right">
 <a href="#old_claimed_patterns-menu">^</a>
@@ -1572,9 +1572,9 @@
           with this issue (<a href="http://issues.apache.org/jira/browse/FOR-217">FOR-217</a>).
         </p>
 </div>
-<a name="N104CD"></a><a name="general"></a>
+<a name="N104CC"></a><a name="general"></a>
 <h3 class="underlined_5">5. General</h3>
-<a name="N104D1"></a><a name="generating_menus"></a>
+<a name="N104D0"></a><a name="generating_menus"></a>
 <h4 class="faq">5.1. What is the relationship between site.xml and book.xml? </h4>
 <div align="right">
 <a href="#generating_menus-menu">^</a>
@@ -1588,7 +1588,7 @@
           <span class="codefrag">site.xml</span>-generated menus aren't appropriate. See <a href="../docs_0_80/linking.html">Menus and
             Linking</a>. </p>
 </div>
-<a name="N104EC"></a><a name="docbook"></a>
+<a name="N104EB"></a><a name="docbook"></a>
 <h4 class="faq">5.2.  How do I use DocBook as the XML documentation format? </h4>
 <div align="right">
 <a href="#docbook-menu">^</a>
@@ -1684,7 +1684,7 @@
           different DTDs, then see <a href="../docs_0_80/howto/../your-project.html#new_dtd">Using Forrest</a> for
           configuration guidance. </p>
 </div>
-<a name="N10525"></a><a name="version"></a>
+<a name="N10524"></a><a name="version"></a>
 <h4 class="faq">5.3.  How to report which version of Forrest is being used and the properties that are
         set? </h4>
 <div align="right">
@@ -1697,7 +1697,7 @@
           watch the build messages. Doing <span class="codefrag">'forrest -v'</span> will provide verbose build
           messages. </p>
 </div>
-<a name="N10539"></a><a name="logs"></a>
+<a name="N10538"></a><a name="logs"></a>
 <h4 class="faq">5.4.  Where are the log files to find more infomation about errors? </h4>
 <div align="right">
 <a href="#logs-menu">^</a>
@@ -1716,7 +1716,7 @@
 <p> Doing <span class="codefrag">'forrest -v'</span> will provide verbose build messages to the standard
           output. </p>
 </div>
-<a name="N1055D"></a><a name="how_can_I_help"></a>
+<a name="N1055C"></a><a name="how_can_I_help"></a>
 <h4 class="faq">5.5.  How to help? </h4>
 <div align="right">
 <a href="#how_can_I_help-menu">^</a>
@@ -1727,7 +1727,7 @@
           particularly from newcomers&mdash;often, close proximity blinds software developers to
           faults that are obvious to everyone else. Don't be shy! </p>
 </div>
-<a name="N10569"></a><a name="patch"></a>
+<a name="N10568"></a><a name="patch"></a>
 <h4 class="faq">5.6.  How to contribute a patch? </h4>
 <div align="right">
 <a href="#patch-menu">^</a>
@@ -1738,7 +1738,7 @@
 <p>More info about contributing can be found at the <a href="../contrib.html">Contributing
             to Forrest</a> page. It is always a good idea to check the Forrest <a href="../issues.html">issue tracker</a> before diving in. </p>
 </div>
-<a name="N10584"></a><a name="jobs"></a>
+<a name="N10583"></a><a name="jobs"></a>
 <h4 class="faq">5.7.  How can job positions be advertised? </h4>
 <div align="right">
 <a href="#jobs-menu">^</a>

Modified: forrest/site/docs_0_80/faq.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/faq.pdf?rev=413268&r1=413267&r2=413268&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/docs_0_80/faq.xml
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_80/faq.xml?rev=413268&r1=413267&r2=413268&view=diff
==============================================================================
--- forrest/site/docs_0_80/faq.xml (original)
+++ forrest/site/docs_0_80/faq.xml Sat Jun 10 01:11:09 2006
@@ -395,7 +395,7 @@
         <p>All internationalistation of tokens in, for example, the skins and the menus, is carried out
         by the <link href="http://cocoon.apache.org/2.1/userdocs/i18nTransformer.html">Cocoon i18n 
         Transformer</link>. You can see an example of how it works in the above linked issue.</p>
-      </section><section id="rawTML"><title>2.19. How can I include HTML content that is not to be skinned by Forrest?</title>
+      </section><section id="rawHTML"><title>2.19. How can I include HTML content that is not to be skinned by Forrest?</title>
         <p>To serve, for example a legacy HTML site, add something like the following 
         to your project's sitemap and place the source content at the
         <code>src/documentation/content/xdocs/old_site/</code> directory.</p>
@@ -420,7 +420,7 @@
           <li>cd seed</li>
           <li>forrest seed-sample</li>
           <li>forrest</li>
-          <li><link href="http://localhost:8888/samples/linking.html#no-decoration">Read the doc</link></li>
+          <li><code>http://localhost:8888/samples/linking.html#no-decoration</code></li>
         </ol>
       </section><section id="javascript"><title>2.20. How to include additional Javascript and CSS files?</title>
         <p>

Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewvc/forrest/site/forrest-issues.html?rev=413268&r1=413267&r2=413268&view=diff
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Sat Jun 10 01:11:09 2006
@@ -192,9 +192,6 @@
 <a href="#%5BFOR-591%5D+MaxMemory+needs+increasing+for+large+document+sets%3A+Memory+Leak+with+XMLFileModule">[FOR-591] MaxMemory needs increasing for large document sets: Memory Leak with XMLFileModule</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-855%5D+verify+the+license+situation+prior+to+each+release">[FOR-855] verify the license situation prior to each release</a>
 </li>
 <li>
@@ -207,9 +204,6 @@
 <a href="#%5BFOR-865%5D+Add+missing+entries+to+status.xml+to+generate+the+changes+list">[FOR-865] Add missing entries to status.xml to generate the changes list</a>
 </li>
 <li>
-<a href="#%5BFOR-891%5D+css-validator+reports+CSS+errors+and+many+warnings+for+pelt+skin">[FOR-891] css-validator reports CSS errors and many warnings for pelt skin</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>
 </li>
 <li>
@@ -263,6 +257,12 @@
 <li>
 <a href="#%5BFOR-726%5D+use+locationmap+in+all+of+the+plugins">[FOR-726] use locationmap in all of the plugins</a>
 </li>
+<li>
+<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-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>
 </ul>
 </div>
 <div class="note">
@@ -293,23 +293,7 @@
 &lt;br/&gt;
 (NB maxmemory has been increased in our site-author/forrest.properties, if we resolve this issue it should be reduced again)</p>
 </div>
-<a name="N1001D"></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>
-<a href="http://issues.apache.org/jira/browse/FOR-713">http://issues.apache.org/jira/browse/FOR-713</a>
-</p>
-<p>html-to-document.xsl no longer converts content to an XDoc. Instead it renders converts documents to XDoc, instead it allows H1, H2 etc. elements to pass through.
-&lt;br/&gt;
-
-&lt;br/&gt;
-The result is a page that seems to render correctly and in the single test case I have used it still renders correctly in PDF and Text format. However, this is a backward incompatible change that will break sites that use includes with XPath statements such as /section[@id=&amp;quot;foo&amp;quot;] (sections are no longer created)
-&lt;br/&gt;
-
-&lt;br/&gt;
-</p>
-</div>
-<a name="N10029"></a><a name="%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release"></a>
+<a name="N1001D"></a><a name="%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release"></a>
 <h2 class="underlined_10">[FOR-855] verify the license situation prior to each release</h2>
 <div class="section">
 <p>
@@ -331,7 +315,7 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N10035"></a><a name="%5BFOR-867%5D+need+doc+to+explain+status+of+skins+and+dispatcher"></a>
+<a name="N10029"></a><a name="%5BFOR-867%5D+need+doc+to+explain+status+of+skins+and+dispatcher"></a>
 <h2 class="underlined_10">[FOR-867] need doc to explain status of skins and dispatcher</h2>
 <div class="section">
 <p>
@@ -343,7 +327,7 @@
 &lt;br/&gt;
 I have already commenced this xdoc.</p>
 </div>
-<a name="N10041"></a><a name="%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc"></a>
+<a name="N10035"></a><a name="%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc"></a>
 <h2 class="underlined_10">[FOR-868] add relevant notes to the "Upgrading" xdoc</h2>
 <div class="section">
 <p>
@@ -351,7 +335,7 @@
 </p>
 <p>We need to add some notes to the upgrading_0*.html doc for the upcoming release. This would most easily be done after attending to &lt;a href="http://issues.apache.org/jira/browse/FOR-865" title="Add missing entries to status.xml to generate the changes list"&gt;FOR-865&lt;/a&gt; &amp;quot;Add missing entries to status.xml to generate the changes list&amp;quot;.</p>
 </div>
-<a name="N1004D"></a><a name="%5BFOR-865%5D+Add+missing+entries+to+status.xml+to+generate+the+changes+list"></a>
+<a name="N10041"></a><a name="%5BFOR-865%5D+Add+missing+entries+to+status.xml+to+generate+the+changes+list"></a>
 <h2 class="underlined_10">[FOR-865] Add missing entries to status.xml to generate the changes list</h2>
 <div class="section">
 <p>
@@ -369,17 +353,7 @@
 &lt;br/&gt;
 &lt;a href="http://marc.theaimsgroup.com/?t=114274836600001"&gt;http://marc.theaimsgroup.com/?t=114274836600001&lt;/a&gt;</p>
 </div>
-<a name="N10059"></a><a name="%5BFOR-891%5D+css-validator+reports+CSS+errors+and+many+warnings+for+pelt+skin"></a>
-<h2 class="underlined_10">[FOR-891] css-validator reports CSS errors and many warnings for pelt skin</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-891">http://issues.apache.org/jira/browse/FOR-891</a>
-</p>
-<p>Our home page does not pass CSS validation with &lt;a href="http://jigsaw.w3.org/css-validator/"&gt;http://jigsaw.w3.org/css-validator/&lt;/a&gt;
-&lt;br/&gt;
-</p>
-</div>
-<a name="N10065"></a><a name="%5BFOR-572%5D+run+a+memory+profiler+while+forrest+is+operating"></a>
+<a name="N1004D"></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>
@@ -387,7 +361,7 @@
 </p>
 <p>We need to run a memory profiler while forrest is operating.</p>
 </div>
-<a name="N10071"></a><a name="%5BFOR-533%5D+Auto+Generate+plugins.xml+entry"></a>
+<a name="N10059"></a><a name="%5BFOR-533%5D+Auto+Generate+plugins.xml+entry"></a>
 <h2 class="underlined_10">[FOR-533] Auto Generate plugins.xml entry</h2>
 <div class="section">
 <p>
@@ -403,7 +377,7 @@
 &lt;br/&gt;
 This change will require that the plugins.xml file be retrieved from the build directory rather than the plugins directory when building the plugin documentation pages. We will therefore need a fall back to retrieve this file from the network if it is not currently available - this can be done with the locationmap</p>
 </div>
-<a name="N1007D"></a><a name="%5BFOR-639%5D+define+terminology+for+the+various+aspects+of+Dispatcher"></a>
+<a name="N10065"></a><a name="%5BFOR-639%5D+define+terminology+for+the+various+aspects+of+Dispatcher"></a>
 <h2 class="underlined_10">[FOR-639] define terminology for the various aspects of Dispatcher</h2>
 <div class="section">
 <p>
@@ -415,7 +389,7 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N10089"></a><a name="%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode"></a>
+<a name="N10071"></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>
@@ -431,7 +405,7 @@
 &lt;br/&gt;
 - the pdf links give an error &amp;quot;Resource Not Found&amp;quot;</p>
 </div>
-<a name="N10095"></a><a name="%5BFOR-711%5D+Cache+results+from+the+Locationmap"></a>
+<a name="N1007D"></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>
@@ -447,7 +421,7 @@
 &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 &lt;a href="http://issues.apache.org/jira/browse/FOR-701" title="Missing locationmap entry gives poor error"&gt;FOR-701&lt;/a&gt;)</p>
 </div>
-<a name="N100A1"></a><a name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
+<a name="N10089"></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>
@@ -461,7 +435,7 @@
 &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="N100AD"></a><a name="%5BFOR-876%5D+locationmap+demo+in+fresh-site+is+broken"></a>
+<a name="N10095"></a><a name="%5BFOR-876%5D+locationmap+demo+in+fresh-site+is+broken"></a>
 <h2 class="underlined_10">[FOR-876] locationmap demo in fresh-site is broken</h2>
 <div class="section">
 <p>
@@ -473,7 +447,7 @@
 &lt;br/&gt;
 &lt;a href="http://marc.theaimsgroup.com/?t=114681865100003"&gt;http://marc.theaimsgroup.com/?t=114681865100003&lt;/a&gt;</p>
 </div>
-<a name="N100B9"></a><a name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
+<a name="N100A1"></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>
@@ -519,7 +493,7 @@
 &lt;br/&gt;
 the ampersand in the link href attribute is not.</p>
 </div>
-<a name="N100C5"></a><a name="%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links"></a>
+<a name="N100AD"></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>
@@ -529,7 +503,7 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N100D1"></a><a name="%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs"></a>
+<a name="N100B9"></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>
@@ -543,7 +517,7 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N100DD"></a><a name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
+<a name="N100C5"></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>
@@ -551,7 +525,7 @@
 </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="N100E9"></a><a name="%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately"></a>
+<a name="N100D1"></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>
@@ -573,7 +547,7 @@
 &lt;br/&gt;
 &amp;nbsp;&amp;nbsp;Lorenz Froihofer.</p>
 </div>
-<a name="N100F5"></a><a name="%5BFOR-200%5D+Locationmap+for+Forrest+and+Users"></a>
+<a name="N100DD"></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>
@@ -585,7 +559,7 @@
 &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="N10101"></a><a name="%5BFOR-546%5D+Sitemap+reference+doc+should+be+updated+to+reflect+plugin+architecture"></a>
+<a name="N100E9"></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>
@@ -617,7 +591,7 @@
 &lt;br/&gt;
 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="N1010D"></a><a name="%5BFOR-560%5D+Remove+duplicate+jars+from+eclipse+plugins"></a>
+<a name="N100F5"></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>
@@ -625,7 +599,7 @@
 </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="N10119"></a><a name="%5BFOR-644%5D+code-style+cleanup+for+xml+files"></a>
+<a name="N10101"></a><a name="%5BFOR-644%5D+code-style+cleanup+for+xml+files"></a>
 <h2 class="underlined_10">[FOR-644] code-style cleanup for xml files</h2>
 <div class="section">
 <p>
@@ -635,7 +609,7 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N10125"></a><a name="%5BFOR-666%5D+clarify+the+sitemap+matches+etc.+in+FAQ+about+non-skinned+html"></a>
+<a name="N1010D"></a><a name="%5BFOR-666%5D+clarify+the+sitemap+matches+etc.+in+FAQ+about+non-skinned+html"></a>
 <h2 class="underlined_10">[FOR-666] clarify the sitemap matches etc. in FAQ about non-skinned html</h2>
 <div class="section">
 <p>
@@ -651,7 +625,7 @@
 &lt;br/&gt;
 &amp;lt;map:match pattern=&amp;quot;old_site/**.html&amp;quot;&amp;gt;</p>
 </div>
-<a name="N10131"></a><a name="%5BFOR-726%5D+use+locationmap+in+all+of+the+plugins"></a>
+<a name="N10119"></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>
@@ -662,6 +636,38 @@
 
 &lt;br/&gt;
 (Perhaps we need Jira sub-tasks for each plugin.)</p>
+</div>
+<a name="N10125"></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-721">http://issues.apache.org/jira/browse/FOR-721</a>
+</p>
+<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 most likely a side-effect of the workaround for issue &lt;a href="http://issues.apache.org/jira/browse/FOR-675" title="upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc."&gt;FOR-675&lt;/a&gt;</p>
+</div>
+<a name="N10131"></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-677">http://issues.apache.org/jira/browse/FOR-677</a>
+</p>
+<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;
+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;
+
+&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;
+
+&lt;br/&gt;
+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>
 </div>
 <!--+

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