Author: crossley
Date: Thu Jul 13 17:55:42 2006
New Revision: 421777
URL: http://svn.apache.org/viewvc?rev=421777&view=rev
Log:
Automatic publish from forrestbot
Modified:
forrest/site/docs_0_80/upgrading_08.html
forrest/site/docs_0_80/upgrading_08.pdf
forrest/site/forrest-issues.html
forrest/site/forrest-issues.pdf
Modified: forrest/site/docs_0_80/upgrading_08.html
URL:
http://svn.apache.org/viewvc/forrest/site/docs_0_80/upgrading_08.html?rev=421777&r1=421776&r2=421777&view=diff
==============================================================================
--- forrest/site/docs_0_80/upgrading_08.html (original)
+++ forrest/site/docs_0_80/upgrading_08.html Thu Jul 13 17:55:42 2006
@@ -342,12 +342,15 @@
<a href="#new">New Features</a>
</li>
<li>
-<a href="#to2to">New filename convention for stylesheets</a>
+<a href="#config">Compare configuration</a>
</li>
<li>
<a href="#clean">Run a clean target after upgrade</a>
</li>
<li>
+<a href="#to2to">New filename convention for stylesheets</a>
+</li>
+<li>
<a href="#tips">General upgrade tips</a>
</li>
<li>
@@ -369,7 +372,7 @@
</div>
<p>
This page describes some changes to Apache Forrest that affect people
who are
- upgrading to the 0.8-dev version.
+ upgrading to the 0.8 version.
If you have other issues, then please discuss on either the
<a href="../mail-lists.html#forrest-dev">dev</a> or
<a href="../mail-lists.html#forrest-user">user</a>
@@ -388,15 +391,27 @@
<h2 class="underlined_10">New Features</h2>
<div class="section">
<p>
- The following list shows some of the key new features
- (for the full list of changes, see the
- <a href="../docs_0_80/changes.html">change log</a>).
+ The following list shows some of the key new features.
+ For the full list of changes, see the main
+ <a href="../docs_0_80/changes.html">change log</a> and also for each
plugin.
</p>
<ul>
-<li>See <a href="../docs_0_80/status-themes.html">Status of Themes: Skins and
Dispatcher</a>.</li>
+<li>
+<a href="../docs_0_80/locationmap.html">Locationmap</a>.</li>
</ul>
+<p>Many new initial plugins are in the "whiteboard". See the entries in the
+ <a href="../docs_0_80/changes.html">change log</a> and see each
plugin's documentation and changes log.
+ This includes the new Dispatcher.
+ See <a href="../docs_0_80/status-themes.html">Status of Themes: Skins
and Dispatcher</a>.
+ </p>
+</div>
+
+
+<a name="N10052"></a><a name="config"></a>
+<h2 class="underlined_10">Compare configuration</h2>
+<div class="section">
<p>
As usual, do a "forrest seed site" in a new directory and compare the
forrest.properties and skinconf.xml with that of your project.
@@ -404,7 +419,17 @@
</div>
-<a name="N1004B"></a><a name="to2to"></a>
+<a name="N1005C"></a><a name="clean"></a>
+<h2 class="underlined_10">Run a clean target after upgrade</h2>
+<div class="section">
+<p>
+ Do 'forrest clean-work' in each of your projects. This also removes
+ the old Cocoon disk cache.
+ </p>
+</div>
+
+
+<a name="N10066"></a><a name="to2to"></a>
<h2 class="underlined_10">New filename convention for stylesheets</h2>
<div class="section">
<p>
@@ -421,17 +446,7 @@
</div>
-<a name="N1005F"></a><a name="clean"></a>
-<h2 class="underlined_10">Run a clean target after upgrade</h2>
-<div class="section">
-<p>
- Do 'forrest clean-work' in each of your projects. This also removes
- the old Cocoon disk cache.
- </p>
-</div>
-
-
-<a name="N10069"></a><a name="tips"></a>
+<a name="N1007A"></a><a name="tips"></a>
<h2 class="underlined_10">General upgrade tips</h2>
<div class="section">
<p>
@@ -450,7 +465,7 @@
</div>
-<a name="N10079"></a><a name="To+be+continued..."></a>
+<a name="N1008A"></a><a name="To+be+continued..."></a>
<h2 class="underlined_10">To be continued...</h2>
<div class="section">
<p>...as more issues are discovered/remembered :) Please send feedback
Modified: forrest/site/docs_0_80/upgrading_08.pdf
URL:
http://svn.apache.org/viewvc/forrest/site/docs_0_80/upgrading_08.pdf?rev=421777&r1=421776&r2=421777&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/forrest-issues.html
URL:
http://svn.apache.org/viewvc/forrest/site/forrest-issues.html?rev=421777&r1=421776&r2=421777&view=diff
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Thu Jul 13 17:55:42 2006
@@ -219,49 +219,49 @@
<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>
+<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-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-666%5D+clarify+the+sitemap+matches+etc.+in+FAQ+about+non-skinned+html">[FOR-666]
clarify the sitemap matches etc. in FAQ about non-skinned html</a>
</li>
<li>
-<a href="#%5BFOR-200%5D+Locationmap+for+Forrest+and+Users">[FOR-200]
Locationmap for Forrest and Users</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-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>
+<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-560%5D+Remove+duplicate+jars+from+eclipse+plugins">[FOR-560]
Remove duplicate jars from eclipse plugins</a>
+<a
href="#%5BFOR-765%5D+forrest+war+gets+NoSuchMethodError+for+some+core+transformer">[FOR-765]
forrest war gets NoSuchMethodError for some core transformer</a>
</li>
<li>
-<a href="#%5BFOR-644%5D+code-style+cleanup+for+xml+files">[FOR-644] code-style
cleanup for xml files</a>
+<a
href="#%5BFOR-772%5D+INvalid+HTML+as+source+causes+unexpected+behaviour">[FOR-772]
INvalid HTML as source causes unexpected behaviour</a>
</li>
<li>
-<a
href="#%5BFOR-666%5D+clarify+the+sitemap+matches+etc.+in+FAQ+about+non-skinned+html">[FOR-666]
clarify the sitemap matches etc. in FAQ about non-skinned html</a>
+<a
href="#%5BFOR-776%5D+rationalise+the+pluginTemplate+and+current+plugins+to+have+minimal+configuration+files%2C+etc.">[FOR-776]
rationalise the pluginTemplate and current plugins to have minimal
configuration files, etc.</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-901%5D+Review+the+note+on+the+home+page+about+first+forrest+run+and+retrieving+plugins+from+network">[FOR-901]
Review the note on the home page about first forrest run and retrieving
plugins from network</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-889%5D+Use+by+Ant+of+newer+catalog+entity+resolver+failing+for+Windows">[FOR-889]
Use by Ant of newer catalog entity resolver failing for Windows</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>
+<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-765%5D+forrest+war+gets+NoSuchMethodError+for+some+core+transformer">[FOR-765]
forrest war gets NoSuchMethodError for some core transformer</a>
+<a href="#%5BFOR-200%5D+Locationmap+for+Forrest+and+Users">[FOR-200]
Locationmap for Forrest and Users</a>
</li>
<li>
-<a
href="#%5BFOR-772%5D+INvalid+HTML+as+source+causes+unexpected+behaviour">[FOR-772]
INvalid HTML as source causes unexpected behaviour</a>
+<a
href="#%5BFOR-906%5D+locationmap+documentation+explain+this-to-that.xsl+naming+convention+and+default+lm+matches">[FOR-906]
locationmap documentation explain this-to-that.xsl naming convention and
default lm matches</a>
</li>
<li>
-<a
href="#%5BFOR-776%5D+rationalise+the+pluginTemplate+and+current+plugins+to+have+minimal+configuration+files%2C+etc.">[FOR-776]
rationalise the pluginTemplate and current plugins to have minimal
configuration files, etc.</a>
+<a href="#%5BFOR-537%5D+Plugin+documentation+sitemap+references">[FOR-537]
Plugin documentation sitemap references</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-671%5D+Layering+error+of+HTML+headings+breaks+rest+of+the+page+w%2Fo+warning">[FOR-671]
Layering error of HTML headings breaks rest of the page w/o warning</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>
+<a
href="#%5BFOR-731%5D+empty+linkmap.html+document%2C+side-effect+of+workaround+to+FOR-675">[FOR-731]
empty linkmap.html document, side-effect of workaround to FOR-675</a>
</li>
</ul>
</div>
@@ -453,37 +453,7 @@
<br/>
the ampersand in the link href attribute is not.</p>
</div>
-<a name="N10089"></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 &quot;fresh-site&quot; build from 'forrest seed site' reports
some failures for faq.html and various missing images. Wonder if sitemap
issue?<br/>
-<br/>
-</p>
-</div>
-<a name="N10095"></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="N100A1"></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.
-<br/>
-
-<br/>
-Beware that it will not work for raw files that are not linked, as this
&quot;feature&quot; currently uses a fixed dir being being copied by
Ant.</p>
-</div>
-<a name="N100AD"></a><a
name="%5BFOR-546%5D+Sitemap+reference+doc+should+be+updated+to+reflect+plugin+architecture"></a>
+<a name="N10089"></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>
@@ -515,25 +485,7 @@
<br/>
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="N100B9"></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-560";>http://issues.apache.org/jira/browse/FOR-560</a>
-</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="N100C5"></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>
-<a
href="http://issues.apache.org/jira/browse/FOR-644";>http://issues.apache.org/jira/browse/FOR-644</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: <a
href="http://marc.theaimsgroup.com/?t=112450901100001">http://marc.theaimsgroup.com/?t=112450901100001</a>
and <a
href="http://marc.theaimsgroup.com/?t=112495618800002">http://marc.theaimsgroup.com/?t=112495618800002</a>
and various linked discussions.
-<br/>
-</p>
-</div>
-<a name="N100D1"></a><a
name="%5BFOR-666%5D+clarify+the+sitemap+matches+etc.+in+FAQ+about+non-skinned+html"></a>
+<a name="N10095"></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>
@@ -549,7 +501,7 @@
<br/>
&lt;map:match pattern=&quot;old_site/**.html&quot;&gt;</p>
</div>
-<a name="N100DD"></a><a
name="%5BFOR-726%5D+use+locationmap+in+all+of+the+plugins"></a>
+<a name="N100A1"></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>
@@ -561,19 +513,7 @@
<br/>
(Perhaps we need Jira sub-tasks for each plugin.)</p>
</div>
-<a name="N100E9"></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 &quot;label&quot; attributes. Previously these documents were
not being generated. Not sure if this change in behaviour is good or bad. Needs
investigation.
-<br/>
-
-<br/>
-This is most likely a side-effect of the workaround for issue <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.">FOR-675</a></p>
-</div>
-<a name="N100F5"></a><a
name="%5BFOR-677%5D+leading+slash+in+gathered+URIs+causes+double+the+number+of+links+to+be+processed"></a>
+<a name="N100AD"></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>
@@ -593,7 +533,7 @@
<br/>
However, we do have a sitemap transformer to &quot;relativize&quot;
and &quot;absolutize&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="N10101"></a><a
name="%5BFOR-765%5D+forrest+war+gets+NoSuchMethodError+for+some+core+transformer"></a>
+<a name="N100B9"></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>
<div class="section">
<p>
@@ -601,7 +541,7 @@
</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>
-<a name="N1010D"></a><a
name="%5BFOR-772%5D+INvalid+HTML+as+source+causes+unexpected+behaviour"></a>
+<a name="N100C5"></a><a
name="%5BFOR-772%5D+INvalid+HTML+as+source+causes+unexpected+behaviour"></a>
<h2 class="underlined_10">[FOR-772] INvalid HTML as source causes unexpected
behaviour</h2>
<div class="section">
<p>
@@ -635,7 +575,7 @@
<br/>
Does such an error get spotted during the validation stage of a
&quot;forrest site&quot; command (execute directly with
&quot;forrest validate&quot;)</p>
</div>
-<a name="N10119"></a><a
name="%5BFOR-776%5D+rationalise+the+pluginTemplate+and+current+plugins+to+have+minimal+configuration+files%2C+etc."></a>
+<a name="N100D1"></a><a
name="%5BFOR-776%5D+rationalise+the+pluginTemplate+and+current+plugins+to+have+minimal+configuration+files%2C+etc."></a>
<h2 class="underlined_10">[FOR-776] rationalise the pluginTemplate and current
plugins to have minimal configuration files, etc.</h2>
<div class="section">
<p>
@@ -665,7 +605,33 @@
<br/>
Tidy up the pluginTempate/status.xml</p>
</div>
-<a name="N10125"></a><a
name="%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs"></a>
+<a name="N100DD"></a><a
name="%5BFOR-901%5D+Review+the+note+on+the+home+page+about+first+forrest+run+and+retrieving+plugins+from+network"></a>
+<h2 class="underlined_10">[FOR-901] Review the note on the home page about
first forrest run and retrieving plugins from network</h2>
+<div class="section">
+<p>
+<a
href="http://issues.apache.org/jira/browse/FOR-901";>http://issues.apache.org/jira/browse/FOR-901</a>
+</p>
+<p>Review the note on the home page about first forrest run and retrieving
plugins from network
+<br/>
+<a
href="http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/index.xml?r1=365495&r2=365494&pathrev=365495">http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/index.xml?r1=365495&amp;r2=365494&amp;pathrev=365495</a></p>
+</div>
+<a name="N100E9"></a><a
name="%5BFOR-889%5D+Use+by+Ant+of+newer+catalog+entity+resolver+failing+for+Windows"></a>
+<h2 class="underlined_10">[FOR-889] Use by Ant of newer catalog entity
resolver failing for Windows</h2>
+<div class="section">
+<p>
+<a
href="http://issues.apache.org/jira/browse/FOR-889";>http://issues.apache.org/jira/browse/FOR-889</a>
+</p>
+<p>Some people on Windows report that the 'forrest validate-xdocs' task is
&quot;failing&quot; when we upgrade the
$FORREST_HOME/tools/ant/lib/xml-commons-resolver.jar
+<br/>
+
+<br/>
+See discussion in:
+<br/>
+&nbsp;[heads up] Ant upgraded, please test
+<br/>
+&nbsp;<a
href="http://marc.theaimsgroup.com/?t=114800390100001">http://marc.theaimsgroup.com/?t=114800390100001</a></p>
+</div>
+<a name="N100F5"></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>
@@ -679,33 +645,125 @@
<br/>
</p>
</div>
-<a name="N10131"></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="N10101"></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-705";>http://issues.apache.org/jira/browse/FOR-705</a>
+<a
href="http://issues.apache.org/jira/browse/FOR-200";>http://issues.apache.org/jira/browse/FOR-200</a>
</p>
-<p>Build fails when given target URL of rewriteDemo is not available (site
down, no longer exists, incorrect URL typing etc).
+<p>The locationmap gives us the ability to specify where sources are, both for
Forrest and for the users.
<br/>
<br/>
-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]
+Beware that it will not work for raw files that are not linked, as this
&quot;feature&quot; currently uses a fixed dir being being copied by
Ant.</p>
+</div>
+<a name="N1010D"></a><a
name="%5BFOR-906%5D+locationmap+documentation+explain+this-to-that.xsl+naming+convention+and+default+lm+matches"></a>
+<h2 class="underlined_10">[FOR-906] locationmap documentation explain
this-to-that.xsl naming convention and default lm matches</h2>
+<div class="section">
+<p>
+<a
href="http://issues.apache.org/jira/browse/FOR-906";>http://issues.apache.org/jira/browse/FOR-906</a>
+</p>
+<p>Explain this-to-that.xsl naming convention and default locationmap
matches.</p>
+</div>
+<a name="N10119"></a><a
name="%5BFOR-537%5D+Plugin+documentation+sitemap+references"></a>
+<h2 class="underlined_10">[FOR-537] Plugin documentation sitemap
references</h2>
+<div class="section">
+<p>
+<a
href="http://issues.apache.org/jira/browse/FOR-537";>http://issues.apache.org/jira/browse/FOR-537</a>
+</p>
+<p>This one references:
+<br/>
+&quot;FORREST_INSTALL_DIR/plugins/sitemap.xmap&quot;
+<br/>
+and
+<br/>
+&quot;src/plugins/sitemap.xmap&quot;
+<br/>
+and
+<br/>
+&quot;&lt;map:mount uri-prefix=&quot;&quot;
+<br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;src=&quot;{forrest:plugins}/sitemap.xmap&quot;:
<br/>
<br/>
-[1] <a
href="http://marc.theaimsgroup.com/?l=forrest-dev&m=112826350500282">http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=112826350500282</a>
+<a
href="http://forrest.apache.org/0.7/docs/plugins/pluginInfrastructure.html#How+does+Installation+work%3F">http://forrest.apache.org/0.7/docs/plugins/pluginInfrastructure.html#How+does+Installation+work%3F</a>
+<br/>
+
<br/>
<br/>
-[2] <a
href="http://marc.theaimsgroup.com/?l=forrest-dev&m=11270994920771">http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=11270994920771</a>
+--tim</p>
+</div>
+<a name="N10125"></a><a
name="%5BFOR-671%5D+Layering+error+of+HTML+headings+breaks+rest+of+the+page+w%2Fo+warning"></a>
+<h2 class="underlined_10">[FOR-671] Layering error of HTML headings breaks
rest of the page w/o warning</h2>
+<div class="section">
+<p>
+<a
href="http://issues.apache.org/jira/browse/FOR-671";>http://issues.apache.org/jira/browse/FOR-671</a>
+</p>
+<p>Up to revision 280144 if you make Forrest display the following file as a
skinned .html-file in Forrest, you'll only see the title. Only if you fix the
layering error of the headings and make h2 into h1 will the rest of the page
content show.
<br/>
<br/>
-[3] <a
href="http://marc.theaimsgroup.com/?l=forrest-dev&m=112859428219336&w=2">http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=112859428219336&amp;w=2</a>
+If Forrest minds this layering error it should at least report it as an error,
shoulnd't it?
<br/>
<br/>
+&lt;?xml version=&quot;1.0&quot;
encoding=&quot;ISO-8859-1&quot;?&gt;
+<br/>
+&lt;!DOCTYPE html PUBLIC &quot;-//W3C//DTD XHTML 1.0
Strict//EN&quot; &quot;<a
href="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd</a>&quot;&gt;
+<br/>
+&lt;html&gt;
+<br/>
+&lt;head&gt;
+<br/>
+&lt;title&gt;Englisch&lt;/title&gt;
+<br/>
+&lt;/head&gt;
+<br/>
+&lt;body class=&quot;Oberbereich&quot;&gt;
+<br/>
+&lt;h2&gt;Kursthemen&lt;/h2&gt;
+<br/>
+&lt;ul class=&quot;Kursthemenliste&quot;&gt;
+<br/>
+&lt;li class=&quot;Kurstthemenlistenpunkt&quot;&gt;
+<br/>
+&lt;a class=&quot;Kursthemenliste_Listenpunkt&quot;
href=&quot;$KursthemaDateiname&quot;&gt;Getting Started in Business
(Abendkurs 1 x w&#xF6;chentlich)
+<br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/a&gt;
+<br/>
+&lt;/li&gt;
+<br/>
+&lt;li class=&quot;Kurstthemenlistenpunkt&quot;&gt;
+<br/>
+&lt;a class=&quot;Kursthemenliste_Listenpunkt&quot;
href=&quot;$KursthemaDateiname&quot;&gt;Getting Ahead in Business
(Abendkurs 1 x w&#xF6;chentlich)
+<br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/a&gt;
+<br/>
+&lt;/li&gt;
+<br/>
+&lt;li class=&quot;Kurstthemenlistenpunkt&quot;&gt;
+<br/>
+&lt;a class=&quot;Kursthemenliste_Listenpunkt&quot;
href=&quot;$KursthemaDateiname&quot;&gt;Complaints, Reports and
other Messages (Wochenendseminar)
+<br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;/a&gt;
+<br/>
+&lt;/li&gt;
+<br/>
+&lt;/ul&gt;
+<br/>
+&lt;/body&gt;
+<br/>
+&lt;/html&gt;</p>
+</div>
+<a name="N10131"></a><a
name="%5BFOR-731%5D+empty+linkmap.html+document%2C+side-effect+of+workaround+to+FOR-675"></a>
+<h2 class="underlined_10">[FOR-731] empty linkmap.html document, side-effect
of workaround to FOR-675</h2>
+<div class="section">
+<p>
+<a
href="http://issues.apache.org/jira/browse/FOR-731";>http://issues.apache.org/jira/browse/FOR-731</a>
</p>
+<p>The main/webapp/resources/stylesheets/linkmap-to-document.xsl has a
workaround for a side-effect to the of the workaround for issue <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.">FOR-675</a>.</p>
</div>
</div>
<!--+
Modified: forrest/site/forrest-issues.pdf
URL:
http://svn.apache.org/viewvc/forrest/site/forrest-issues.pdf?rev=421777&r1=421776&r2=421777&view=diff
==============================================================================
Binary files - no diff available.
