Author: crossley
Date: Wed Jul 12 16:28:33 2006
New Revision: 421459
URL: http://svn.apache.org/viewvc?rev=421459&view=rev
Log:
Automatic publish from forrestbot
Modified:
forrest/site/committed.html
forrest/site/committed.pdf
forrest/site/forrest-issues.html
forrest/site/forrest-issues.pdf
forrest/site/howto-dev.html
forrest/site/howto-dev.pdf
Modified: forrest/site/committed.html
URL:
http://svn.apache.org/viewvc/forrest/site/committed.html?rev=421459&r1=421458&r2=421459&view=diff
==============================================================================
--- forrest/site/committed.html (original)
+++ forrest/site/committed.html Wed Jul 12 16:28:33 2006
@@ -231,7 +231,7 @@
<input value="+a" class="biggerfont" title="Enlarge
text" onclick="ndeSetTextSize('incr'); return false;" type="button">
</div>
<h1>Becoming an Apache Forrest committer</h1>
-<div class="abstract">This is a discussion of how users can progress to
+<div class="abstract">This is a discussion of how users can
become committers within the Apache Forrest project.</div>
<div id="minitoc-area">
<ul class="minitoc">
@@ -281,11 +281,10 @@
<p>One thing
that is sometimes hard to understand when you are new to the
open development<sup>1</sup> process used at the ASF,
- is that we care more about the community than the code.
- This is because a strong and healthy
- community will usually generate strong and healthy code. As a result
- of the Apache focus on community it is more important for people here
- to discuss and explore within the community.</p>
+ is that we value the community more than the code.
+ A strong and healthy community will be respectful and be a fun
+ and rewarding place. Strong code will evolve.
+ </p>
</div>
<a name="N1002A"></a><a name="copdoc"></a>
Modified: forrest/site/committed.pdf
URL:
http://svn.apache.org/viewvc/forrest/site/committed.pdf?rev=421459&r1=421458&r2=421459&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=421459&r1=421458&r2=421459&view=diff
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Wed Jul 12 16:28:33 2006
@@ -189,9 +189,6 @@
<div id="minitoc-area">
<ul class="minitoc">
<li>
-<a
href="#%5BFOR-591%5D+MaxMemory+needs+increasing+for+large+document+sets%3A+Memory+Leak+with+XMLFileModule">[FOR-591]
MaxMemory needs increasing for large document sets: Memory Leak with
XMLFileModule</a>
-</li>
-<li>
<a
href="#%5BFOR-867%5D+need+doc+to+explain+status+of+skins+and+dispatcher">[FOR-867]
need doc to explain status of skins and dispatcher</a>
</li>
<li>
@@ -204,15 +201,9 @@
<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-572%5D+run+a+memory+profiler+while+forrest+is+operating">[FOR-572]
run a memory profiler while forrest is operating</a>
-</li>
-<li>
<a href="#%5BFOR-533%5D+Auto+Generate+plugins.xml+entry">[FOR-533] Auto
Generate plugins.xml entry</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>
-</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>
</li>
<li>
@@ -222,6 +213,9 @@
<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-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-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>
@@ -263,6 +257,12 @@
<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>
</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>
+<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>
<div class="note">
@@ -273,27 +273,7 @@
<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-591%5D+MaxMemory+needs+increasing+for+large+document+sets%3A+Memory+Leak+with+XMLFileModule"></a>
-<h2 class="underlined_10">[FOR-591] MaxMemory needs increasing for large
document sets: Memory Leak with XMLFileModule</h2>
-<div class="section">
-<p>
-<a
href="http://issues.apache.org/jira/browse/FOR-591";>http://issues.apache.org/jira/browse/FOR-591</a>
-</p>
-<p>Since the docs restructuring for the 0.7 release it has become necessary to
increase the maxmemory to be able to build the Forrest site. We gained three
copies of the documents so suddenly have a large document set to trigger memory
leakage issues.
-<br/>
-
-<br/>
-Possibly <a href="http://issues.apache.org/jira/browse/COCOON-1574";
title="Memory Leak with XMLFileModule">COCOON-1574</a>
&quot;Memory Leak with XMLFileModule&quot;.
-<br/>
-
-<br/>
-Does someone have the tools to run some diagnostics?
-<br/>
-
-<br/>
-(NB maxmemory has been increased in our site-author/forrest.properties, if we
resolve this issue it should be reduced again)</p>
-</div>
-<a name="N1001D"></a><a
name="%5BFOR-867%5D+need+doc+to+explain+status+of+skins+and+dispatcher"></a>
+<a name="N10011"></a><a
name="%5BFOR-867%5D+need+doc+to+explain+status+of+skins+and+dispatcher"></a>
<h2 class="underlined_10">[FOR-867] need doc to explain status of skins and
dispatcher</h2>
<div class="section">
<p>
@@ -305,7 +285,7 @@
<br/>
I have already commenced this xdoc.</p>
</div>
-<a name="N10029"></a><a
name="%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc"></a>
+<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>
@@ -313,7 +293,7 @@
</p>
<p>We need to add some notes to the upgrading_0*.html doc for the upcoming
release. This would most easily be done after attending to <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-865%5D+Add+missing+entries+to+status.xml+to+generate+the+changes+list"></a>
+<a name="N10029"></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>
@@ -331,7 +311,7 @@
<br/>
<a
href="http://marc.theaimsgroup.com/?t=114274836600001">http://marc.theaimsgroup.com/?t=114274836600001</a></p>
</div>
-<a name="N10041"></a><a
name="%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release"></a>
+<a name="N10035"></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>
@@ -353,15 +333,7 @@
<br/>
</p>
</div>
-<a name="N1004D"></a><a
name="%5BFOR-572%5D+run+a+memory+profiler+while+forrest+is+operating"></a>
-<h2 class="underlined_10">[FOR-572] run a memory profiler while forrest is
operating</h2>
-<div class="section">
-<p>
-<a
href="http://issues.apache.org/jira/browse/FOR-572";>http://issues.apache.org/jira/browse/FOR-572</a>
-</p>
-<p>We need to run a memory profiler while forrest is operating.</p>
-</div>
-<a name="N10059"></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>
@@ -377,19 +349,7 @@
<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="N10065"></a><a
name="%5BFOR-639%5D+define+terminology+for+the+various+aspects+of+Dispatcher"></a>
-<h2 class="underlined_10">[FOR-639] define terminology for the various aspects
of Dispatcher</h2>
-<div class="section">
-<p>
-<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="N10071"></a><a
name="%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode"></a>
+<a name="N1004D"></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>
@@ -405,7 +365,7 @@
<br/>
- the pdf links give an error &quot;Resource Not Found&quot;</p>
</div>
-<a name="N1007D"></a><a
name="%5BFOR-711%5D+Cache+results+from+the+Locationmap"></a>
+<a name="N10059"></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>
@@ -421,7 +381,7 @@
<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 <a
href="http://issues.apache.org/jira/browse/FOR-701"; title="Missing locationmap
entry gives poor error">FOR-701</a>)</p>
</div>
-<a name="N10089"></a><a
name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
+<a name="N10065"></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>
@@ -435,7 +395,19 @@
<br/>
<a
href="http://marc.theaimsgroup.com/?t=113176328300002">http://marc.theaimsgroup.com/?t=113176328300002</a></p>
</div>
-<a name="N10095"></a><a
name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
+<a name="N10071"></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="N1007D"></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>
@@ -481,7 +453,7 @@
<br/>
the ampersand in the link href attribute is not.</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>
+<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>
@@ -491,7 +463,7 @@
<br/>
</p>
</div>
-<a name="N100AD"></a><a
name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
+<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>
@@ -499,7 +471,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="N100B9"></a><a
name="%5BFOR-200%5D+Locationmap+for+Forrest+and+Users"></a>
+<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>
@@ -511,7 +483,7 @@
<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="N100C5"></a><a
name="%5BFOR-546%5D+Sitemap+reference+doc+should+be+updated+to+reflect+plugin+architecture"></a>
+<a name="N100AD"></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>
@@ -543,7 +515,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="N100D1"></a><a
name="%5BFOR-560%5D+Remove+duplicate+jars+from+eclipse+plugins"></a>
+<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>
@@ -551,7 +523,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="N100DD"></a><a
name="%5BFOR-644%5D+code-style+cleanup+for+xml+files"></a>
+<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>
@@ -561,7 +533,7 @@
<br/>
</p>
</div>
-<a name="N100E9"></a><a
name="%5BFOR-666%5D+clarify+the+sitemap+matches+etc.+in+FAQ+about+non-skinned+html"></a>
+<a name="N100D1"></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>
@@ -577,7 +549,7 @@
<br/>
&lt;map:match pattern=&quot;old_site/**.html&quot;&gt;</p>
</div>
-<a name="N100F5"></a><a
name="%5BFOR-726%5D+use+locationmap+in+all+of+the+plugins"></a>
+<a name="N100DD"></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>
@@ -589,7 +561,7 @@
<br/>
(Perhaps we need Jira sub-tasks for each plugin.)</p>
</div>
-<a name="N10101"></a><a
name="%5BFOR-721%5D+entries+without+labels+in+site.xml+are+now+being+crawled+and+generated"></a>
+<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>
@@ -601,7 +573,7 @@
<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="N1010D"></a><a
name="%5BFOR-677%5D+leading+slash+in+gathered+URIs+causes+double+the+number+of+links+to+be+processed"></a>
+<a name="N100F5"></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>
@@ -621,7 +593,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="N10119"></a><a
name="%5BFOR-765%5D+forrest+war+gets+NoSuchMethodError+for+some+core+transformer"></a>
+<a name="N10101"></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>
@@ -629,7 +601,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="N10125"></a><a
name="%5BFOR-772%5D+INvalid+HTML+as+source+causes+unexpected+behaviour"></a>
+<a name="N1010D"></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>
@@ -663,7 +635,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="N10131"></a><a
name="%5BFOR-776%5D+rationalise+the+pluginTemplate+and+current+plugins+to+have+minimal+configuration+files%2C+etc."></a>
+<a name="N10119"></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>
@@ -692,6 +664,48 @@
<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>
+<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-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>
+</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>
+<div class="section">
+<p>
+<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).
+<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]
+<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>
+<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>
+<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>
+<br/>
+
+<br/>
+</p>
</div>
</div>
<!--+
Modified: forrest/site/forrest-issues.pdf
URL:
http://svn.apache.org/viewvc/forrest/site/forrest-issues.pdf?rev=421459&r1=421458&r2=421459&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/howto-dev.html
URL:
http://svn.apache.org/viewvc/forrest/site/howto-dev.html?rev=421459&r1=421458&r2=421459&view=diff
==============================================================================
--- forrest/site/howto-dev.html (original)
+++ forrest/site/howto-dev.html Wed Jul 12 16:28:33 2006
@@ -325,6 +325,12 @@
<li>
<a href="#tips-debug">Tips</a>
</li>
+<li>
+<a href="#profile-yourkit">Profiling Forrest with YourKit</a>
+</li>
+<li>
+<a href="#profile-netbeans">Profiling Forrest with Netbeans</a>
+</li>
</ul>
</li>
<li>
@@ -891,13 +897,52 @@
</li>
</ul>
-<a name="N10246"></a><a name="find"></a>
+<div class="note">
+<div class="label">Note</div>
+<div class="content">
+ The next two sections describe the configuration of profiling tools
but they are not
+ integrated with the IDE. If you can figure out how to properly
configure the for
+ integrated operation with the IDE, please provide a documentation
patch.
+ </div>
+</div>
+<a name="N10248"></a><a name="profile-yourkit"></a>
+<h4>Profiling Forrest with YourKit</h4>
+<p>
+ Assuming you have the YourKit software installed you simply need to
do two things to
+ profile a particular Forrest Project. First, you need to add
*YourKit Home*\bin\win32 to
+ your PATH environment variable - where *YourKit Home* is the
installation directory of that
+ software. Next you need to add the following to your
forrest.properties file for the project.
+ </p>
+<pre class="code">forrest.jvmargs=-agentlib:yjpagent</pre>
+<p>
+ You are now all set, simply type 'forrest run', then open up YourKit
and select "Connect
+ to locally running profiled application...". If you don't see the
types of objects that you
+ expected, check the current filters - YourKit seems to filter out
org.apache.* namespaces by
+ default.
+ </p>
+<a name="N10259"></a><a name="profile-netbeans"></a>
+<h4>Profiling Forrest with Netbeans</h4>
+<p>
+ Assuming you have the Netbeans IDE installed you simply need to do a
couple things to
+ profile a particular Forrest Project. First, you need to add
+ *Netbeans Home*\profiler1\lib\deployed\jdk142\windows to your path.
Obviously, this needs
+ to be slightly modified for a Unix machine. Now, you need to add
the following line to your
+ forrest.properties file for the project (replacing *NetbeansHome*
with the path to your install).
+ </p>
+<pre
class="code">forrest.jvmargs=-agentpath:C:\*NetbeansHome*\\profiler1\\lib\\deployed\\jdk15\\windows\\
+profilerinterface.dll=\C:\\*NetbeansHome*\\profiler1\\lib\\,5140</pre>
+<p>
+ You are now all set, simply type 'forrest run', then open up the
Netbeans IDE with your Forrest
+ project. Click Profile->Attach Profiler and make selections
appropriate to what you are trying
+ to achieve.
+ </p>
+<a name="N1026B"></a><a name="find"></a>
<h3 class="underlined_5">Finding the relevant sources</h3>
<p>
You will need to be able to find which sources, sitemaps, stylesheets
are responsible for certain processing.
</p>
-<a name="N1024F"></a><a name="find-scenario-1"></a>
+<a name="N10274"></a><a name="find-scenario-1"></a>
<h4>Scenario: How does i18n work</h4>
<p>
We will do a search for "i18n" to start with, then refine that after
@@ -940,7 +985,7 @@
is declared to use i18n, then further down the page the "skinit"
pipeline uses the i18n transformer only if i18n is switched on.
</p>
-<a name="N10271"></a><a name="tips-find"></a>
+<a name="N10296"></a><a name="tips-find"></a>
<h4>Tips</h4>
<ul>
@@ -950,31 +995,31 @@
</ul>
</div>
-<a name="N10281"></a><a name="Frequently Asked Questions"></a>
+<a name="N102A6"></a><a name="Frequently Asked Questions"></a>
<h2 class="underlined_10">Frequently Asked Questions</h2>
<div class="section">
-<a name="N10285"></a><a name="1+General+issues"></a>
+<a name="N102AA"></a><a name="1+General+issues"></a>
<h3 class="underlined_5">1 General issues</h3>
-<a name="N10289"></a><a name="1.1+FAQ+1"></a>
+<a name="N102AE"></a><a name="1.1+FAQ+1"></a>
<h4>1.1 FAQ 1</h4>
<p>
####
</p>
-<a name="N10291"></a><a name="2+Other+issues"></a>
+<a name="N102B6"></a><a name="2+Other+issues"></a>
<h3 class="underlined_5">2 Other issues</h3>
-<a name="N10295"></a><a name="2.1+FAQ+2.1"></a>
+<a name="N102BA"></a><a name="2.1+FAQ+2.1"></a>
<h4>2.1 FAQ 2.1</h4>
<p>
###
</p>
</div>
-<a name="N1029D"></a><a name="Tips"></a>
+<a name="N102C2"></a><a name="Tips"></a>
<h2 class="underlined_10">Tips</h2>
<div class="section">
<p>
This is a collection of general tips that do not fit in the sections
above.
</p>
-<a name="N102A5"></a><a name="tip-howto"></a>
+<a name="N102CA"></a><a name="tip-howto"></a>
<h3 class="underlined_5">Explanations about howto topics on the mailing
lists</h3>
<p>
Often there are useful discussions on the mailing lists which explain
@@ -983,7 +1028,7 @@
which links to the email discussion. Later someone else can summarise.
</p>
</div>
-<a name="N102AF"></a><a name="References"></a>
+<a name="N102D4"></a><a name="References"></a>
<h2 class="underlined_10">References</h2>
<div class="section">
<p>
Modified: forrest/site/howto-dev.pdf
URL:
http://svn.apache.org/viewvc/forrest/site/howto-dev.pdf?rev=421459&r1=421458&r2=421459&view=diff
==============================================================================
Binary files - no diff available.
