Author: crossley
Date: Sun Nov 26 16:16:25 2006
New Revision: 479473
URL: http://svn.apache.org/viewvc?view=rev&rev=479473
Log:
Automatic publish from forrestbot
Modified:
forrest/site/doap.xml
forrest/site/forrest-issues.html
forrest/site/forrest-issues.pdf
Modified: forrest/site/doap.xml
URL:
http://svn.apache.org/viewvc/forrest/site/doap.xml?view=diff&rev=479473&r1=479472&r2=479473
==============================================================================
--- forrest/site/doap.xml (original)
+++ forrest/site/doap.xml Sun Nov 26 16:16:25 2006
@@ -66,7 +66,6 @@
</doap:description>
<doap:programming-language
xml:lang="en">Java</doap:programming-language>
- <doap:programming-language
xml:lang="en">XML</doap:programming-language>
<doap:category
rdf:resource="http://projects.apache.org/category/build-management"/>
<doap:category
rdf:resource="http://projects.apache.org/category/database"/>
<doap:category
rdf:resource="http://projects.apache.org/category/graphics"/>
Modified: forrest/site/forrest-issues.html
URL:
http://svn.apache.org/viewvc/forrest/site/forrest-issues.html?view=diff&rev=479473&r1=479472&r2=479473
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Sun Nov 26 16:16:25 2006
@@ -189,22 +189,22 @@
<div id="minitoc-area">
<ul class="minitoc">
<li>
-<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>
+<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>
-<a
href="#%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc">[FOR-868]
add relevant notes to the "Upgrading" xdoc</a>
+<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-855%5D+verify+the+license+situation+prior+to+each+release">[FOR-855]
verify the license situation prior to each release</a>
+<a
href="#%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc">[FOR-868]
add relevant notes to the "Upgrading" xdoc</a>
</li>
<li>
<a href="#%5BFOR-911%5D+decide+content+of+release">[FOR-911] decide content of
release</a>
</li>
<li>
-<a
href="#%5BFOR-639%5D+define+terminology+for+the+various+aspects+of+Dispatcher">[FOR-639]
define terminology for the various aspects of Dispatcher</a>
+<a href="#%5BFOR-533%5D+Auto+Generate+plugins.xml+entry">[FOR-533] Auto
Generate plugins.xml entry</a>
</li>
<li>
-<a href="#%5BFOR-533%5D+Auto+Generate+plugins.xml+entry">[FOR-533] Auto
Generate plugins.xml entry</a>
+<a
href="#%5BFOR-639%5D+define+terminology+for+the+various+aspects+of+Dispatcher">[FOR-639]
define terminology for the various aspects of Dispatcher</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>
@@ -222,31 +222,34 @@
<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-644%5D+code-style+cleanup+for+xml+files">[FOR-644] code-style
cleanup for xml files</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>
</li>
<li>
<a href="#%5BFOR-726%5D+use+locationmap+in+all+of+the+plugins">[FOR-726] use
locationmap in all of the plugins</a>
</li>
<li>
-<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>
+<a href="#%5BFOR-765%5D+forrest+war+and+classpath+issues+with+Jetty">[FOR-765]
forrest war and classpath issues with Jetty</a>
</li>
<li>
-<a
href="#%5BFOR-922%5D+update+all+docs+that+explain+sitemap+fragments">[FOR-922]
update all docs that explain sitemap fragments</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-936%5D+Forrest+%22looses%22+the+locale+when+switching+pages">[FOR-936]
Forrest "looses" the locale when switching pages</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-644%5D+code-style+cleanup+for+xml+files">[FOR-644] code-style
cleanup for xml files</a>
+<a
href="#%5BFOR-922%5D+update+all+docs+that+explain+sitemap+fragments">[FOR-922]
update all docs that explain sitemap fragments</a>
</li>
<li>
-<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>
+<a
href="#%5BFOR-936%5D+Forrest+%22looses%22+the+locale+when+switching+pages">[FOR-936]
Forrest "looses" the locale when switching pages</a>
</li>
<li>
-<a href="#%5BFOR-765%5D+forrest+war+and+classpath+issues+with+Jetty">[FOR-765]
forrest war and classpath issues with Jetty</a>
+<a href="#%5BFOR-537%5D+Plugin+documentation+sitemap+references">[FOR-537]
Plugin documentation sitemap references</a>
</li>
<li>
-<a href="#%5BFOR-537%5D+Plugin+documentation+sitemap+references">[FOR-537]
Plugin documentation sitemap references</a>
+<a
href="#%5BFOR-635%5D+images+not+reproduced+in+PDFs%2C+if+sources+are+in+xdocs%2Fimages+directory">[FOR-635]
images not reproduced in PDFs, if sources are in xdocs/images directory</a>
</li>
<li>
<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>
@@ -260,9 +263,6 @@
<li>
<a
href="#%5BFOR-861%5D+Update+locationmap+docs+for+working+with+remote+files">[FOR-861]
Update locationmap docs for working with remote files</a>
</li>
-<li>
-<a
href="#%5BFOR-635%5D+images+not+reproduced+in+PDFs%2C+if+sources+are+in+xdocs%2Fimages+directory">[FOR-635]
images not reproduced in PDFs, if sources are in xdocs/images directory</a>
-</li>
</ul>
</div>
<div class="note">
@@ -273,53 +273,53 @@
<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-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>
+<a name="N10011"></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>
-<a
href="http://issues.apache.org/jira/browse/FOR-865";>http://issues.apache.org/jira/browse/FOR-865</a>
+<a
href="http://issues.apache.org/jira/browse/FOR-855";>http://issues.apache.org/jira/browse/FOR-855</a>
</p>
-<p>There are insufficient entries in our site-author/status.xml to generate
the changes.html for the upcoming release.
+<p>This should be continually happening anyway, but immediately prior to each
release we need to verify that our license situation is in order. This issue
should not ever be closed, rather just move the &quot;Fix for
Version&quot; on to the next release.
<br/>
<br/>
-Besides informing users of the major changes and providing cross-links to the
issue tracker, this file also provides recognition of contributions ... at the
moment there are too few. It also has the importance=high attribute, which
generates our release announcement ... again, too few.
+Here are some of the tasks:
<br/>
<br/>
-Re: better use of changes.html (Was: Community health)
+A) Ensure that all supporting libraries have a corresponding license.
Basically every jar file or other external package needs to have a
*.license.txt file. Ensure that any license conditions are met, e.g. for some
we must add an entry to NOTICE.txt, while for some others we must not. Remember
to abide by the ASF guidelines (e.g. nothing more restrictive than the Apache
License).
+<br/>
+
+<br/>
+B) Scan the whole trunk repository to add missing ASF license headers to
source files and to ensure that the ASF license headers have not been
accidently added to external files. See etc/relicense.txt
<br/>
-<a
href="http://marc.theaimsgroup.com/?t=114274836600001">http://marc.theaimsgroup.com/?t=114274836600001</a></p>
-</div>
-<a name="N1001D"></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>
-<a
href="http://issues.apache.org/jira/browse/FOR-868";>http://issues.apache.org/jira/browse/FOR-868</a>
</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 <a
href="http://issues.apache.org/jira/browse/FOR-865"; title="Add missing entries
to status.xml to generate the changes list">FOR-865</a> &quot;Add
missing entries to status.xml to generate the changes list&quot;.</p>
</div>
-<a name="N10029"></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>
+<a name="N1001D"></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>
-<a
href="http://issues.apache.org/jira/browse/FOR-855";>http://issues.apache.org/jira/browse/FOR-855</a>
+<a
href="http://issues.apache.org/jira/browse/FOR-865";>http://issues.apache.org/jira/browse/FOR-865</a>
</p>
-<p>This should be continually happening anyway, but immediately prior to each
release we need to verify that our license situation is in order. This issue
should not ever be closed, rather just move the &quot;Fix for
Version&quot; on to the next release.
-<br/>
-
-<br/>
-Here are some of the tasks:
+<p>There are insufficient entries in our site-author/status.xml to generate
the changes.html for the upcoming release.
<br/>
<br/>
-A) Ensure that all supporting libraries have a corresponding license.
Basically every jar file or other external package needs to have a
*.license.txt file. Ensure that any license conditions are met, e.g. for some
we must add an entry to NOTICE.txt, while for some others we must not. Remember
to abide by the ASF guidelines (e.g. nothing more restrictive than the Apache
License).
+Besides informing users of the major changes and providing cross-links to the
issue tracker, this file also provides recognition of contributions ... at the
moment there are too few. It also has the importance=high attribute, which
generates our release announcement ... again, too few.
<br/>
<br/>
-B) Scan the whole trunk repository to add missing ASF license headers to
source files and to ensure that the ASF license headers have not been
accidently added to external files. See etc/relicense.txt
+Re: better use of changes.html (Was: Community health)
<br/>
+<a
href="http://marc.theaimsgroup.com/?t=114274836600001">http://marc.theaimsgroup.com/?t=114274836600001</a></p>
+</div>
+<a name="N10029"></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>
+<a
href="http://issues.apache.org/jira/browse/FOR-868";>http://issues.apache.org/jira/browse/FOR-868</a>
</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 <a
href="http://issues.apache.org/jira/browse/FOR-865"; title="Add missing entries
to status.xml to generate the changes list">FOR-865</a> &quot;Add
missing entries to status.xml to generate the changes list&quot;.</p>
</div>
<a name="N10035"></a><a name="%5BFOR-911%5D+decide+content+of+release"></a>
<h2 class="underlined_10">[FOR-911] decide content of release</h2>
@@ -337,19 +337,7 @@
<br/>
&nbsp;<a
href="http://marc.theaimsgroup.com/?t=115257903800001">http://marc.theaimsgroup.com/?t=115257903800001</a></p>
</div>
-<a name="N10041"></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>
-<a
href="http://issues.apache.org/jira/browse/FOR-639";>http://issues.apache.org/jira/browse/FOR-639</a>
-</p>
-<p>See the email thread:
-<br/>
-<a
href="http://marc.theaimsgroup.com/?t=112276643700001">http://marc.theaimsgroup.com/?t=112276643700001</a>
-<br/>
-</p>
-</div>
-<a name="N1004D"></a><a
name="%5BFOR-533%5D+Auto+Generate+plugins.xml+entry"></a>
+<a name="N10041"></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>
@@ -365,6 +353,18 @@
<br/>
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="N1004D"></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>
+<a
href="http://issues.apache.org/jira/browse/FOR-639";>http://issues.apache.org/jira/browse/FOR-639</a>
+</p>
+<p>See the email thread:
+<br/>
+<a
href="http://marc.theaimsgroup.com/?t=112276643700001">http://marc.theaimsgroup.com/?t=112276643700001</a>
+<br/>
+</p>
+</div>
<a name="N10059"></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">
@@ -485,7 +485,17 @@
<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="N10095"></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-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="N100A1"></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>
@@ -501,7 +511,7 @@
<br/>
&lt;map:match pattern=&quot;old_site/**.html&quot;&gt;</p>
</div>
-<a name="N100A1"></a><a
name="%5BFOR-726%5D+use+locationmap+in+all+of+the+plugins"></a>
+<a name="N100AD"></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>
@@ -513,7 +523,25 @@
<br/>
(Perhaps we need Jira sub-tasks for each plugin.)</p>
</div>
-<a name="N100AD"></a><a
name="%5BFOR-906%5D+locationmap+documentation+explain+this-to-that.xsl+naming+convention+and+default+lm+matches"></a>
+<a name="N100B9"></a><a
name="%5BFOR-765%5D+forrest+war+and+classpath+issues+with+Jetty"></a>
+<h2 class="underlined_10">[FOR-765] forrest war and classpath issues with
Jetty</h2>
+<div class="section">
+<p>
+<a
href="http://issues.apache.org/jira/browse/FOR-765";>http://issues.apache.org/jira/browse/FOR-765</a>
+</p>
+<p>Until recently we could run forrest as a WAR with Jetty. 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'. This indicates a classpath issue with
Jetty/Forrest configuration.</p>
+</div>
+<a name="N100C5"></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="N100D1"></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>
@@ -521,7 +549,7 @@
</p>
<p>Explain this-to-that.xsl naming convention and default locationmap
matches.</p>
</div>
-<a name="N100B9"></a><a
name="%5BFOR-922%5D+update+all+docs+that+explain+sitemap+fragments"></a>
+<a name="N100DD"></a><a
name="%5BFOR-922%5D+update+all+docs+that+explain+sitemap+fragments"></a>
<h2 class="underlined_10">[FOR-922] update all docs that explain sitemap
fragments</h2>
<div class="section">
<p>
@@ -537,7 +565,7 @@
<br/>
These changes need to be reflected in the current docs.</p>
</div>
-<a name="N100C5"></a><a
name="%5BFOR-936%5D+Forrest+%22looses%22+the+locale+when+switching+pages"></a>
+<a name="N100E9"></a><a
name="%5BFOR-936%5D+Forrest+%22looses%22+the+locale+when+switching+pages"></a>
<h2 class="underlined_10">[FOR-936] Forrest "looses" the locale when switching
pages</h2>
<div class="section">
<p>
@@ -565,34 +593,6 @@
<br/>
The fix is simple, patch to come soon.</p>
</div>
-<a name="N100D1"></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="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-765%5D+forrest+war+and+classpath+issues+with+Jetty"></a>
-<h2 class="underlined_10">[FOR-765] forrest war and classpath issues with
Jetty</h2>
-<div class="section">
-<p>
-<a
href="http://issues.apache.org/jira/browse/FOR-765";>http://issues.apache.org/jira/browse/FOR-765</a>
-</p>
-<p>Until recently we could run forrest as a WAR with Jetty. 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'. This indicates a classpath issue with
Jetty/Forrest configuration.</p>
-</div>
<a name="N100F5"></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">
@@ -623,7 +623,15 @@
<br/>
--tim</p>
</div>
-<a name="N10101"></a><a
name="%5BFOR-671%5D+Layering+error+of+HTML+headings+breaks+rest+of+the+page+w%2Fo+warning"></a>
+<a name="N10101"></a><a
name="%5BFOR-635%5D+images+not+reproduced+in+PDFs%2C+if+sources+are+in+xdocs%2Fimages+directory"></a>
+<h2 class="underlined_10">[FOR-635] images not reproduced in PDFs, if sources
are in xdocs/images directory</h2>
+<div class="section">
+<p>
+<a
href="http://issues.apache.org/jira/browse/FOR-635";>http://issues.apache.org/jira/browse/FOR-635</a>
+</p>
+<p>We used to enable images to be placed in the xdocs/images directory.
However, now they are intended to go in the resources/images directory instead.
Both methods will work for html pages, but only the latter method for the PDF
pages.</p>
+</div>
+<a name="N1010D"></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>
@@ -685,7 +693,7 @@
<br/>
&lt;/html&gt;</p>
</div>
-<a name="N1010D"></a><a
name="%5BFOR-731%5D+empty+linkmap.html+document%2C+side-effect+of+workaround+to+FOR-675"></a>
+<a name="N10119"></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>
@@ -693,7 +701,7 @@
</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>
-<a name="N10119"></a><a
name="%5BFOR-767%5D+Forrestbot+webapp+reports+succesful+even+when+there+are+broken+links"></a>
+<a name="N10125"></a><a
name="%5BFOR-767%5D+Forrestbot+webapp+reports+succesful+even+when+there+are+broken+links"></a>
<h2 class="underlined_10">[FOR-767] Forrestbot webapp reports succesful even
when there are broken links</h2>
<div class="section">
<p>
@@ -711,7 +719,7 @@
<br/>
</p>
</div>
-<a name="N10125"></a><a
name="%5BFOR-861%5D+Update+locationmap+docs+for+working+with+remote+files"></a>
+<a name="N10131"></a><a
name="%5BFOR-861%5D+Update+locationmap+docs+for+working+with+remote+files"></a>
<h2 class="underlined_10">[FOR-861] Update locationmap docs for working with
remote files</h2>
<div class="section">
<p>
@@ -730,14 +738,6 @@
[2] <a
href="http://forrest.apache.org/docs_0_80/locationmap.html#namingConvention">http://forrest.apache.org/docs_0_80/locationmap.html#namingConvention</a>
<br/>
[3] <a
href="http://marc.theaimsgroup.com/?t=114492612100001&r=1&w=2">http://marc.theaimsgroup.com/?t=114492612100001&amp;r=1&amp;w=2</a></p>
-</div>
-<a name="N10131"></a><a
name="%5BFOR-635%5D+images+not+reproduced+in+PDFs%2C+if+sources+are+in+xdocs%2Fimages+directory"></a>
-<h2 class="underlined_10">[FOR-635] images not reproduced in PDFs, if sources
are in xdocs/images directory</h2>
-<div class="section">
-<p>
-<a
href="http://issues.apache.org/jira/browse/FOR-635";>http://issues.apache.org/jira/browse/FOR-635</a>
-</p>
-<p>We used to enable images to be placed in the xdocs/images directory.
However, now they are intended to go in the resources/images directory instead.
Both methods will work for html pages, but only the latter method for the PDF
pages.</p>
</div>
</div>
<!--+
Modified: forrest/site/forrest-issues.pdf
URL:
http://svn.apache.org/viewvc/forrest/site/forrest-issues.pdf?view=diff&rev=479473&r1=479472&r2=479473
==============================================================================
Binary files - no diff available.
