Author: crossley
Date: Sun Mar 5 17:29:59 2006
New Revision: 383447
URL: http://svn.apache.org/viewcvs?rev=383447&view=rev
Log:
Automatic publish from forrestbot
Modified:
forrest/site/docs_0_70/primer.pdf
forrest/site/docs_0_80/howto/howto-buildPlugin.html
forrest/site/docs_0_80/howto/howto-buildPlugin.pdf
forrest/site/forrest-issues.html
forrest/site/forrest-issues.pdf
forrest/site/thanks.html
forrest/site/thanks.pdf
Modified: forrest/site/docs_0_70/primer.pdf
URL:
http://svn.apache.org/viewcvs/forrest/site/docs_0_70/primer.pdf?rev=383447&r1=383446&r2=383447&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/docs_0_80/howto/howto-buildPlugin.html
URL:
http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-buildPlugin.html?rev=383447&r1=383446&r2=383447&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-buildPlugin.html (original)
+++ forrest/site/docs_0_80/howto/howto-buildPlugin.html Sun Mar 5 17:29:59 2006
@@ -719,8 +719,14 @@
The files plugins/plugins.xml and whiteboard/plugins/plugins.xml are
the "Plugins Descriptor" files. Each plugin is described with its
name, purpose, location, and version information. These descriptors
- are deployed to the forrest website so that your application can
- manage its plugins.
+ are deployed to the forrest website.
+ </p>
+<p>
+ Each plugin has a build.xml file which defines its version
information.
+ Please keep that synchronised with the plugins.xml files.
+ Later
+ <a href="http://issues.apache.org/jira/browse/FOR-533";>FOR-533</a>
+ will generate this from the various build.xml files.
</p>
<p>
The Apache Forrest committers manage these files in SVN and publish
@@ -738,7 +744,7 @@
<li>Edit the skinconf.xml to ensure that all version numbers are "0.7", e.g.
the MOTD.</li>
-<li>Edit the plugins descriptor to ensure that the "forrestVersion" is 0.7 and
that the "version" is appropriate. </li>
+<li>Edit the plugin's descriptors to ensure that the "forrestVersion" is 0.7
and that the "version" is appropriate. </li>
<li>Ensure that the "website" parameter includes "pluginDocs/plugins_0_70"</li>
@@ -757,7 +763,7 @@
<li>Edit the skinconf.xml to ensure that all version numbers are
"0.8-dev", e.g. the MOTD.</li>
-<li>Edit the plugins descriptor to ensure that the "forrestVersion" is
+<li>Edit the plugin's descriptors to ensure that the "forrestVersion" is
0.8 and that the "version" is incremented. </li>
<li>Ensure that the "website" parameter includes "pluginDocs/plugins_0_80"</li>
@@ -766,7 +772,7 @@
Start adding changes notes.</li>
</ul>
-<a name="N1021A"></a><a name="experimental"></a>
+<a name="N10221"></a><a name="experimental"></a>
<h3 class="underlined_5">Experimental Functionality</h3>
<div class="warning">
<div class="label">Warning</div>
@@ -781,14 +787,14 @@
<div class="content">For an example of each of these features in use see the
<span class="codefrag">org.apache.forrest.internal.NoteTaking</span>
plugin.</div>
</div>
-<a name="N10229"></a><a name="Locationmap"></a>
+<a name="N10230"></a><a name="Locationmap"></a>
<h4>Locationmap</h4>
<p>Plugins can use the Forrest locationmap to expose resources to your
project and other plgins. To use this functionality add your
<span class="codefrag">locationmap.xml</span> file to the root of the
plugin directory.</p>
<p>We have an <a href="http://issues.apache.org/jira/browse/FOR-200";>issue</a>
for the status of locationmap development.</p>
-<a name="N1023D"></a><a name="Dispatcher"></a>
+<a name="N10244"></a><a name="Dispatcher"></a>
<h4>Dispatcher</h4>
<p>Dispatcher (previous codename Forrest Views) is the collective name for the
various pieces of functionality
that are intended to replace skins in the future. They allow for a
much more
@@ -809,35 +815,35 @@
your plugin.</p>
<p>Once Dispatcher becomes stable we will add this match to the default
locationmap
which is generated when you seed a new plugin, but for now it must be
done manually.</p>
-<a name="N1025D"></a><a name="Plugin+Properties"></a>
+<a name="N10264"></a><a name="Plugin+Properties"></a>
<h4>Plugin Properties</h4>
<p>Plugins can define properties that each project can over-ride.
For more information see the issue below.</p>
<p>We have an <a href="http://issues.apache.org/jira/browse/FOR-588";>issue</a>
for the status of this new configuration system.</p>
-<a name="N1026F"></a><a name="examples"></a>
+<a name="N10276"></a><a name="examples"></a>
<h3 class="underlined_5">Examples</h3>
<p>This section will provide some example plugins to help illustrate the
steps discussed above.</p>
-<a name="N10278"></a><a name="input"></a>
+<a name="N1027F"></a><a name="input"></a>
<h4>Input Plugin</h4>
<div class="fixme">
<div class="label">Fixme (RDG)</div>
<div class="content">Discuss OpenOffice.org plugin here</div>
</div>
-<a name="N10283"></a><a name="output"></a>
+<a name="N1028A"></a><a name="output"></a>
<h4>Output Plugin</h4>
<div class="fixme">
<div class="label">Fixme (RDG)</div>
<div class="content">Discuss s5 plugin here</div>
</div>
-<a name="N1028E"></a><a name="internal"></a>
+<a name="N10295"></a><a name="internal"></a>
<h4>Internal Plugin</h4>
<div class="fixme">
<div class="label">Fixme (RDG)</div>
<div class="content">Discuss IMSManifest plugin here</div>
</div>
-<a name="N1029A"></a><a name="extension"></a>
+<a name="N102A1"></a><a name="extension"></a>
<h3 class="underlined_5">Further Reading</h3>
<ul>
@@ -848,7 +854,7 @@
<a href="../../pluginDocs/plugins_0_80/">Plugins Documentation</a> for
users</li>
</ul>
-<a name="N102B0"></a><a name="summarise"></a>
+<a name="N102B7"></a><a name="summarise"></a>
<h3 class="underlined_5">Summarise the Entire Process</h3>
<div class="fixme">
<div class="label">Fixme (open)</div>
Modified: forrest/site/docs_0_80/howto/howto-buildPlugin.pdf
URL:
http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-buildPlugin.pdf?rev=383447&r1=383446&r2=383447&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/forrest-issues.html
URL:
http://svn.apache.org/viewcvs/forrest/site/forrest-issues.html?rev=383447&r1=383446&r2=383447&view=diff
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Sun Mar 5 17:29:59 2006
@@ -202,31 +202,31 @@
<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-707%5D+Document+i18n+features+of+Forrest">[FOR-707] Document
i18n features of Forrest</a>
+<a href="#%5BFOR-533%5D+Auto+Generate+plugins.xml+entry">[FOR-533] Auto
Generate plugins.xml entry</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-711%5D+Cache+results+from+the+Locationmap">[FOR-711] Cache
results from the Locationmap</a>
+<a href="#%5BFOR-707%5D+Document+i18n+features+of+Forrest">[FOR-707] Document
i18n features of Forrest</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-711%5D+Cache+results+from+the+Locationmap">[FOR-711] Cache
results from the Locationmap</a>
</li>
<li>
-<a href="#%5BFOR-533%5D+Auto+Generate+plugins.xml+entry">[FOR-533] Auto
Generate plugins.xml entry</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-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-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-211%5D+whole-site+html+and+pdf%3A+broken+ext+links">[FOR-211]
whole-site html and pdf: broken ext links</a>
</li>
<li>
<a
href="#%5BFOR-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-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-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-203%5D+2nd+level+tabs+are+not+selected+appropriately">[FOR-203]
2nd level tabs are not selected appropriately</a>
@@ -244,10 +244,10 @@
<a href="#%5BFOR-562%5D+Update+Plugins+howto">[FOR-562] Update Plugins
howto</a>
</li>
<li>
-<a href="#%5BFOR-644%5D+whitespace+cleanup">[FOR-644] whitespace cleanup</a>
+<a href="#%5BFOR-645%5D+patches+for+whitespace+cleanup">[FOR-645] patches for
whitespace cleanup</a>
</li>
<li>
-<a href="#%5BFOR-645%5D+patches+for+whitespace+cleanup">[FOR-645] patches for
whitespace cleanup</a>
+<a href="#%5BFOR-644%5D+whitespace+cleanup">[FOR-644] whitespace cleanup</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>
@@ -363,87 +363,87 @@
<br>
</p>
</div>
-<a name="N1004D"></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="N1004D"></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>
-<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-533";>http://issues.apache.org/jira/browse/FOR-533</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.
-<br>
-
-<br>
-Cheche wrote a blog entry on his work:
+<p>The information in the plugins.xml file would be better kept in the plugin
directory and added to the plugins.xml file when deployed. This would reduce
the amount of duplication in the plugins config files.
<br>
<br>
-<a
href="http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/">http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/</a>
+All the necessary values are now in the plugin build.xml file.
<br>
<br>
-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>
+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="N10059"></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>
+<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">
<p>
-<a
href="http://issues.apache.org/jira/browse/FOR-742";>http://issues.apache.org/jira/browse/FOR-742</a>
+<a
href="http://issues.apache.org/jira/browse/FOR-735";>http://issues.apache.org/jira/browse/FOR-735</a>
</p>
-<p>The plugin retrieval and deployment process are not quite correct. Recently
the projectInfo plugin had its version number incremented and the
&quot;unversioned&quot; plugin now relates specifically to 0.8-dev
version. That prevents 0.7 from accessing the relevant plugin.
+<p>(At this point I didn't try this scenario step by step any more; basically
it is what we did to setup the site, except that we copied our project data
from forrest 0.6 before trying the pdf links)
<br>
<br>
-The solution is discussed here:
+- run forrest webapp to create an empty webapp
<br>
-<a
href="http://marc.theaimsgroup.com/?t=113176328300002">http://marc.theaimsgroup.com/?t=113176328300002</a></p>
+- configure Tomcat to run the webapp (we did it by creating a context
descriptor and put it onder Tomcat's config directory)
+<br>
+- the pdf links give an error &quot;Resource Not Found&quot;</p>
</div>
-<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>
+<a name="N10065"></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-711";>http://issues.apache.org/jira/browse/FOR-711</a>
+<a
href="http://issues.apache.org/jira/browse/FOR-707";>http://issues.apache.org/jira/browse/FOR-707</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>There is next to no documentation about i18n, just a pretty poor FAQ entry
that points at an issue that has now been closed.
<br>
<br>
-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.
+Cheche wrote a blog entry on his work:
<br>
<br>
-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>
+<a
href="http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/">http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/</a>
+<br>
+
+<br>
+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="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>
+<a name="N10071"></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-735";>http://issues.apache.org/jira/browse/FOR-735</a>
+<a
href="http://issues.apache.org/jira/browse/FOR-711";>http://issues.apache.org/jira/browse/FOR-711</a>
</p>
-<p>(At this point I didn't try this scenario step by step any more; basically
it is what we did to setup the site, except that we copied our project data
from forrest 0.6 before trying the pdf links)
+<p>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.
<br>
<br>
-- run forrest webapp to create an empty webapp
+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.
<br>
-- configure Tomcat to run the webapp (we did it by creating a context
descriptor and put it onder Tomcat's config directory)
+
<br>
-- the pdf links give an error &quot;Resource Not Found&quot;</p>
+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="N1007D"></a><a
name="%5BFOR-533%5D+Auto+Generate+plugins.xml+entry"></a>
-<h2 class="underlined_10">[FOR-533] Auto Generate plugins.xml entry</h2>
+<a name="N1007D"></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-533";>http://issues.apache.org/jira/browse/FOR-533</a>
+<a
href="http://issues.apache.org/jira/browse/FOR-742";>http://issues.apache.org/jira/browse/FOR-742</a>
</p>
-<p>The information in the plugins.xml file would be better kept in the plugin
directory and added to the plugins.xml file when deployed. This would reduce
the amount of duplication in the plugins config files.
+<p>The plugin retrieval and deployment process are not quite correct. Recently
the projectInfo plugin had its version number incremented and the
&quot;unversioned&quot; plugin now relates specifically to 0.8-dev
version. That prevents 0.7 from accessing the relevant plugin.
<br>
<br>
-All the necessary values are now in the plugin build.xml file.
-<br>
-
+The solution is discussed here:
<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>
+<a
href="http://marc.theaimsgroup.com/?t=113176328300002">http://marc.theaimsgroup.com/?t=113176328300002</a></p>
</div>
<a name="N10089"></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>
@@ -491,19 +491,13 @@
<br>
the ampersand in the link href attribute is not.</p>
</div>
-<a name="N10095"></a><a
name="%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs"></a>
-<h2 class="underlined_10">[FOR-209] First level selected tab is not
highlighted when containing 2nd level tabs</h2>
+<a name="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-209";>http://issues.apache.org/jira/browse/FOR-209</a>
-</p>
-<p>When there are two levels of tabs, the selected first level tab does not
get highlighted, nor are there any other visual or structural clues as to which
first-level tab is active, and which contains the displayed 2nd level tabs.
-<br>
-
-<br>
-This is checked with both the default skin, and with tigris-style.
-<br>
+<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-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>
@@ -515,13 +509,19 @@
<br>
</p>
</div>
-<a name="N100AD"></a><a
name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
-<h2 class="underlined_10">[FOR-211] whole-site html and pdf: broken ext
links</h2>
+<a name="N100AD"></a><a
name="%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs"></a>
+<h2 class="underlined_10">[FOR-209] First level selected tab is not
highlighted when containing 2nd level tabs</h2>
<div class="section">
<p>
-<a
href="http://issues.apache.org/jira/browse/FOR-211";>http://issues.apache.org/jira/browse/FOR-211</a>
+<a
href="http://issues.apache.org/jira/browse/FOR-209";>http://issues.apache.org/jira/browse/FOR-209</a>
+</p>
+<p>When there are two levels of tabs, the selected first level tab does not
get highlighted, nor are there any other visual or structural clues as to which
first-level tab is active, and which contains the displayed 2nd level tabs.
+<br>
+
+<br>
+This is checked with both the default skin, and with tigris-style.
+<br>
</p>
-<p>In the the generated site.html all of the external links are broken (i.e.
the href attributes are like ... error:#ext:forrest).</p>
</div>
<a name="N100B9"></a><a
name="%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately"></a>
<h2 class="underlined_10">[FOR-203] 2nd level tabs are not selected
appropriately</h2>
@@ -625,7 +625,15 @@
<br>
</p>
</div>
-<a name="N100F5"></a><a name="%5BFOR-644%5D+whitespace+cleanup"></a>
+<a name="N100F5"></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="N10101"></a><a name="%5BFOR-644%5D+whitespace+cleanup"></a>
<h2 class="underlined_10">[FOR-644] whitespace cleanup</h2>
<div class="section">
<p>
@@ -636,14 +644,6 @@
<br>
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="N10101"></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="N1010D"></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>
Modified: forrest/site/forrest-issues.pdf
URL:
http://svn.apache.org/viewcvs/forrest/site/forrest-issues.pdf?rev=383447&r1=383446&r2=383447&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/thanks.html
URL:
http://svn.apache.org/viewcvs/forrest/site/thanks.html?rev=383447&r1=383446&r2=383447&view=diff
==============================================================================
--- forrest/site/thanks.html (original)
+++ forrest/site/thanks.html Sun Mar 5 17:29:59 2006
@@ -245,7 +245,8 @@
<a href="http://www.jetbrains.com/idea/opensource/";>IntelliJ IDEA</a>
or
<a href="http://www.eclipse.org/";>Eclipse</a>.
- Most tools do not require attribution, but some do ...
+ Most tools do not require attribution, but some do
+ (<a href="http://www.yourkit.com/";>YourKit Java Profiler</a>).
</p>
</div>
Modified: forrest/site/thanks.pdf
URL:
http://svn.apache.org/viewcvs/forrest/site/thanks.pdf?rev=383447&r1=383446&r2=383447&view=diff
==============================================================================
Binary files - no diff available.
