forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r359661 - in /forrest/site: forrest-issues.html forrest-issues.pdf live-sites.html live-sites.pdf
Date Wed, 28 Dec 2005 23:03:03 GMT
Author: crossley
Date: Wed Dec 28 15:02:54 2005
New Revision: 359661

URL: http://svn.apache.org/viewcvs?rev=359661&view=rev
Log:
Automatic publish from forrestbot

Modified:
    forrest/site/forrest-issues.html
    forrest/site/forrest-issues.pdf
    forrest/site/live-sites.html
    forrest/site/live-sites.pdf

Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-issues.html?rev=359661&r1=359660&r2=359661&view=diff
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Wed Dec 28 15:02:54 2005
@@ -186,33 +186,39 @@
 <div id="minitoc-area">
 <ul class="minitoc">
 <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>
+<a href="#%5BFOR-591%5D+MaxMemory+needs+increasing">[FOR-591] MaxMemory needs increasing</a>
 </li>
 <li>
-<a href="#%5BFOR-591%5D+MaxMemory+needs+increasing">[FOR-591] MaxMemory needs increasing</a>
+<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-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-711%5D+Cache+results+from+the+Locationmap">[FOR-711] Cache results
from the Locationmap</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-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-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-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode">[FOR-735]
Plugins are not correctly deployed in webapp mode</a>
+<a href="#%5BFOR-707%5D+Document+i18n+features+of+Forrest">[FOR-707] Document i18n
features of Forrest</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-711%5D+Cache+results+from+the+Locationmap">[FOR-711] Cache results
from the Locationmap</a>
 </li>
 <li>
-<a href="#%5BFOR-707%5D+Document+i18n+features+of+Forrest">[FOR-707] Document i18n
features of Forrest</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-771%5D+bin%2Fforrest%3A+Incomplete+symlink+resolution+and+incorrect+argument+passing">[FOR-771]
bin/forrest: Incomplete symlink resolution and incorrect argument passing</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>
 </li>
 <li>
+<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-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>
@@ -222,6 +228,9 @@
 <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-200%5D+Locationmap+for+Forrest+and+Users">[FOR-200] Locationmap for
Forrest and Users</a>
+</li>
+<li>
 <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>
@@ -231,34 +240,25 @@
 <a href="#%5BFOR-562%5D+Update+Plugins+howto">[FOR-562] Update Plugins howto</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>
-<li>
-<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-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>
+<a href="#%5BFOR-645%5D+patches+for+whitespace+cleanup">[FOR-645] patches for whitespace
cleanup</a>
 </li>
 <li>
 <a href="#%5BFOR-644%5D+whitespace+cleanup">[FOR-644] whitespace cleanup</a>
 </li>
 <li>
-<a href="#%5BFOR-645%5D+patches+for+whitespace+cleanup">[FOR-645] patches for whitespace
cleanup</a>
-</li>
-<li>
-<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>
+<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-200%5D+Locationmap+for+Forrest+and+Users">[FOR-200] Locationmap for
Forrest and Users</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-726%5D+use+locationmap+in+all+of+the+plugins">[FOR-726] use locationmap
in all of the plugins</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-699%5D+Beginner+HowTos+for+installing+Forrest">[FOR-699] Beginner
HowTos for installing Forrest</a>
 </li>
 <li>
-<a href="#%5BFOR-765%5D+forrest+war+gets+NoSuchMethodError+for+some+core+transformer">[FOR-765]
forrest war gets NoSuchMethodError for some core transformer</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>
 </ul>
 </div>
@@ -270,41 +270,41 @@
        <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-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>
+<a name="N10011"></a><a name="%5BFOR-591%5D+MaxMemory+needs+increasing"></a>
+<h2 class="underlined_10">[FOR-591] MaxMemory needs increasing</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-713">http://issues.apache.org/jira/browse/FOR-713</a>
+<a href="http://issues.apache.org/jira/browse/FOR-591">http://issues.apache.org/jira/browse/FOR-591</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.
+<p>Since the docs restructurng for the 0.7 release it has become necessary to increase
the maxmemory to be able to build the Forrest site.
 &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)
+Does this indicate a memory leak?
 &lt;br&gt;
 
 &lt;br&gt;
-</p>
+Does someone have the tools to run some diagnostics?
+&lt;br&gt;
+
+&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="N1001F"></a><a name="%5BFOR-591%5D+MaxMemory+needs+increasing"></a>
-<h2 class="underlined_10">[FOR-591] MaxMemory needs increasing</h2>
+<a name="N1001F"></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-591">http://issues.apache.org/jira/browse/FOR-591</a>
+<a href="http://issues.apache.org/jira/browse/FOR-713">http://issues.apache.org/jira/browse/FOR-713</a>
 </p>
-<p>Since the docs restructurng for the 0.7 release it has become necessary to increase
the maxmemory to be able to build the Forrest site.
-&lt;br&gt;
-
-&lt;br&gt;
-Does this indicate a memory leak?
+<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;
-Does someone have the tools to run some diagnostics?
+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;
-(NB maxmemory has been increased in forrest.properties, if we resolve this issue it should
be reduced again)</p>
+</p>
 </div>
 <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>
@@ -338,37 +338,23 @@
 &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="N1003B"></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="N1003B"></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-711">http://issues.apache.org/jira/browse/FOR-711</a>
+<a href="http://issues.apache.org/jira/browse/FOR-388">http://issues.apache.org/jira/browse/FOR-388</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>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;
-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.
+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;
-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="N10049"></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;
-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="N10057"></a><a name="%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode"></a>
+<a name="N10049"></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>
@@ -384,43 +370,75 @@
 &lt;br&gt;
 - the pdf links give an error &amp;quot;Resource Not Found&amp;quot;</p>
 </div>
-<a name="N10065"></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>
+<a name="N10057"></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>
-<a href="http://issues.apache.org/jira/browse/FOR-388">http://issues.apache.org/jira/browse/FOR-388</a>
+<a href="http://issues.apache.org/jira/browse/FOR-707">http://issues.apache.org/jira/browse/FOR-707</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.
+<p>There is next to no documentation about i18n, just a pretty poor FAQ entry that
points at an issue that has now been closed.
 &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)
+Cheche wrote a blog entry on his work:
 &lt;br&gt;
 
 &lt;br&gt;
-</p>
+&lt;a href="http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/"&gt;http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/&lt;/a&gt;
+&lt;br&gt;
+
+&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="N10073"></a><a name="%5BFOR-707%5D+Document+i18n+features+of+Forrest"></a>
-<h2 class="underlined_10">[FOR-707] Document i18n features of Forrest</h2>
+<a name="N10065"></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-707">http://issues.apache.org/jira/browse/FOR-707</a>
+<a href="http://issues.apache.org/jira/browse/FOR-711">http://issues.apache.org/jira/browse/FOR-711</a>
 </p>
-<p>There is next to no documentation about i18n, just a pretty poor FAQ entry that
points at an issue that has now been closed.
+<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;
-Cheche wrote a blog entry on his work:
+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;
-&lt;a href="http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/"&gt;http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/&lt;/a&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="N10073"></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;
-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>
+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="N10081"></a><a name="%5BFOR-771%5D+bin%2Fforrest%3A+Incomplete+symlink+resolution+and+incorrect+argument+passing"></a>
+<h2 class="underlined_10">[FOR-771] bin/forrest: Incomplete symlink resolution and
incorrect argument passing</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-771">http://issues.apache.org/jira/browse/FOR-771</a>
+</p>
+<p>Issues in bin/forrest:
+&lt;br&gt;
+1. The symlink resolution does not handle chained symlinks
+&lt;br&gt;
+2. The value assigned to FORREST_HOME is not canonical
+&lt;br&gt;
+3. Command line arguments are passed to ant as $@ instead of &amp;quot;$@&amp;quot;
+&lt;br&gt;
+
+&lt;br&gt;
+The attached patch bin_forrest.diff fixes these issues and is against SVN HEAD (rev. 232917).
The symlink resolution code is less verbose than before (borrowed from the Ant launch script).</p>
 </div>
-<a name="N10081"></a><a name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
+<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>
@@ -466,7 +484,17 @@
 &lt;br&gt;
 the ampersand in the link href attribute is not.</p>
 </div>
-<a name="N1008F"></a><a name="%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs"></a>
+<a name="N1009D"></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-210">http://issues.apache.org/jira/browse/FOR-210</a>
+</p>
+<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;
+</p>
+</div>
+<a name="N100AB"></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>
@@ -480,7 +508,7 @@
 &lt;br&gt;
 </p>
 </div>
-<a name="N1009D"></a><a name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
+<a name="N100B9"></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>
@@ -488,7 +516,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="N100AB"></a><a name="%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately"></a>
+<a name="N100C7"></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>
@@ -510,7 +538,19 @@
 &lt;br&gt;
 &amp;nbsp;&amp;nbsp;Lorenz Froihofer.</p>
 </div>
-<a name="N100B9"></a><a name="%5BFOR-546%5D+Sitemap+reference+doc+should+be+updated+to+reflect+plugin+architecture"></a>
+<a name="N100D5"></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-200">http://issues.apache.org/jira/browse/FOR-200</a>
+</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="N100E3"></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>
@@ -542,7 +582,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="N100C7"></a><a name="%5BFOR-560%5D+Remove+duplicate+jars+from+eclipse+plugins"></a>
+<a name="N100F1"></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>
@@ -550,7 +590,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="N100D5"></a><a name="%5BFOR-562%5D+Update+Plugins+howto"></a>
+<a name="N100FF"></a><a name="%5BFOR-562%5D+Update+Plugins+howto"></a>
 <h2 class="underlined_10">[FOR-562] Update Plugins howto</h2>
 <div class="section">
 <p>
@@ -578,55 +618,39 @@
 &lt;br&gt;
 </p>
 </div>
-<a name="N100E3"></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>
+<a name="N1010D"></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-677">http://issues.apache.org/jira/browse/FOR-677</a>
+<a href="http://issues.apache.org/jira/browse/FOR-645">http://issues.apache.org/jira/browse/FOR-645</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>
+<p>Use this issue to provide patches for the whitespace cleanup.</p>
 </div>
-<a name="N100F1"></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>
+<a name="N1011B"></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-705">http://issues.apache.org/jira/browse/FOR-705</a>
+<a href="http://issues.apache.org/jira/browse/FOR-644">http://issues.apache.org/jira/browse/FOR-644</a>
 </p>
-<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;
-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;
-[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;
-[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;
+<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;
-[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;
+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="N10129"></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-726">http://issues.apache.org/jira/browse/FOR-726</a>
+</p>
+<p>Each plugin has sitemaps that need to use the locationmap.
 &lt;br&gt;
 
 &lt;br&gt;
-</p>
+(Perhaps we need Jira sub-tasks for each plugin.)</p>
 </div>
-<a name="N100FF"></a><a name="%5BFOR-721%5D+entries+without+labels+in+site.xml+are+now+being+crawled+and+generated"></a>
+<a name="N10137"></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>
@@ -638,59 +662,25 @@
 &lt;br&gt;
 This is most likely a side-effect of the workaround for issue FOR-675</p>
 </div>
-<a name="N1010D"></a><a name="%5BFOR-644%5D+whitespace+cleanup"></a>
-<h2 class="underlined_10">[FOR-644] whitespace cleanup</h2>
+<a name="N10145"></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-644">http://issues.apache.org/jira/browse/FOR-644</a>
+<a href="http://issues.apache.org/jira/browse/FOR-677">http://issues.apache.org/jira/browse/FOR-677</a>
 </p>
-<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
+<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 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="N1011B"></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="N10129"></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-210">http://issues.apache.org/jira/browse/FOR-210</a>
-</p>
-<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;
-</p>
-</div>
-<a name="N10137"></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-200">http://issues.apache.org/jira/browse/FOR-200</a>
-</p>
-<p>The locationmap gives us the ability to specify where sources are, both for Forrest
and for the users.
+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;
-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="N10145"></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-726">http://issues.apache.org/jira/browse/FOR-726</a>
-</p>
-<p>Each plugin has sitemaps that need to use the locationmap.
+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;
-(Perhaps we need Jira sub-tasks for each plugin.)</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="N10153"></a><a name="%5BFOR-699%5D+Beginner+HowTos+for+installing+Forrest"></a>
 <h2 class="underlined_10">[FOR-699] Beginner HowTos for installing Forrest</h2>
@@ -700,13 +690,33 @@
 </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="N10161"></a><a name="%5BFOR-765%5D+forrest+war+gets+NoSuchMethodError+for+some+core+transformer"></a>
-<h2 class="underlined_10">[FOR-765] forrest war gets NoSuchMethodError for some core
transformer</h2>
+<a name="N10161"></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-765">http://issues.apache.org/jira/browse/FOR-765</a>
+<a href="http://issues.apache.org/jira/browse/FOR-705">http://issues.apache.org/jira/browse/FOR-705</a>
+</p>
+<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;
+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;
+[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;
+[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;
+[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;
 </p>
-<p>Until recently we could run forrest as a WAR. With today's SVN r356945 it gets past
the Cocoon startup phase, then on the first client request it suffers some error which causes
a NoSuchMethodError. See attached log ... no other clues. This happens for any site, e.g.
'forrest seed-sample war'. All is okay for 'forrest seed-sample run'.</p>
 </div>
 </div>
 <!--+

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

Modified: forrest/site/live-sites.html
URL: http://svn.apache.org/viewcvs/forrest/site/live-sites.html?rev=359661&r1=359660&r2=359661&view=diff
==============================================================================
--- forrest/site/live-sites.html (original)
+++ forrest/site/live-sites.html Wed Dec 28 15:02:54 2005
@@ -441,12 +441,17 @@
         - Software company specialising in optimisation techniques
         using evolutionary algorithms
       </li>
+      
+<li>
+<a href="http://www.art-painter.com/">Snjezana Vidovic - Art Painter</a>
+        - Virtual Gallery
+      </li>
 <!--  <li><link href=""></link></li> -->
     
 </ul>
 </div>
     
-<a name="N1017E"></a><a name="dispatcher"></a>
+<a name="N10184"></a><a name="dispatcher"></a>
 <h2 class="underlined_10">Sites using upcoming Dispatcher</h2>
 <div class="section">
 <p>The skinning system in versions of Forrest up to and including 0.7 was great,

Modified: forrest/site/live-sites.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/live-sites.pdf?rev=359661&r1=359660&r2=359661&view=diff
==============================================================================
Binary files - no diff available.



Mime
View raw message