forrest-site-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r813336 - in /forrest/site: docs_0_90/faq.html docs_0_90/faq.xml forrest-issues.html guidelines.html procedures/release/How_to_release.html tasks.html
Date Thu, 10 Sep 2009 09:55:22 GMT
Author: crossley
Date: Thu Sep 10 09:55:21 2009
New Revision: 813336

URL: http://svn.apache.org/viewvc?rev=813336&view=rev
Log:
update tasks doc

Modified:
    forrest/site/docs_0_90/faq.html
    forrest/site/docs_0_90/faq.xml
    forrest/site/forrest-issues.html
    forrest/site/guidelines.html
    forrest/site/procedures/release/How_to_release.html
    forrest/site/tasks.html

Modified: forrest/site/docs_0_90/faq.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_90/faq.html?rev=813336&r1=813335&r2=813336&view=diff
==============================================================================
--- forrest/site/docs_0_90/faq.html (original)
+++ forrest/site/docs_0_90/faq.html Thu Sep 10 09:55:21 2009
@@ -1192,20 +1192,19 @@
 <a name="N102F3"></a><a name="i18n"></a>
 <h3 class="underlined_5">2.20. How can I internationalise (i18n) my content?</h3>
 <p>
-          The i18n features of Forrest are still under development (as of 0.7)
-          however there are some features available. For example, navigation
-          menus can be i18n'd (see fresh-site for an example). Currently,
-          <a href="http://issues.apache.org/jira/browse/FOR-506">work is
-          underway</a> to i18n skins
+          For example, navigation
+          menus can be internationalized and different content can be served.
         </p>
 <p>
-          All internationalistation of tokens in, for example, the skins and the
-          menus, is carried out by the
+          There is an example to demonstrate and explain the facilities.
+          See a 'forrest seed-sample' site.
+        </p>
+<p>
+          All internationalisation of tokens is carried out by the
           <a href="http://cocoon.apache.org/2.1/userdocs/i18nTransformer.html">Cocoon
-          i18n Transformer</a>. You can see an example of how it works in the
-          above linked issue.
+          i18n Transformer</a>.
         </p>
-<a name="N10306"></a><a name="rawHTML"></a>
+<a name="N10305"></a><a name="rawHTML"></a>
 <h3 class="underlined_5">2.21. How can I include HTML content that is not to be skinned by Forrest?</h3>
 <p>
           To serve, for example a legacy HTML site, add something like the
@@ -1253,7 +1252,7 @@
 </li>
         
 </ol>
-<a name="N10332"></a><a name="javascript"></a>
+<a name="N10331"></a><a name="javascript"></a>
 <h3 class="underlined_5">2.22. How to include additional Javascript and CSS files?</h3>
 <p>
           Place various resources (e.g. javascript, css) into the "project
@@ -1270,7 +1269,7 @@
           forrest/main/webapp/resources.xmap Search for "javascript" then follow
           to the &lt;map:resource name="skin-read"&gt; section.
         </p>
-<a name="N10340"></a><a name="linkmap"></a>
+<a name="N1033F"></a><a name="linkmap"></a>
 <h3 class="underlined_5">2.23. How to show a Table Of Contents for the whole site?</h3>
 <p>
           Every site has an automatically generated document at
@@ -1294,10 +1293,10 @@
           project.start-uri in the forrest.properties file.
         </p>
 </div>
-<a name="N1035E"></a><a name="technical"></a>
+<a name="N1035D"></a><a name="technical"></a>
 <h2 class="underlined_10">3. Technical</h2>
 <div class="section">
-<a name="N10362"></a><a name="java-code"></a>
+<a name="N10361"></a><a name="java-code"></a>
 <h3 class="underlined_5">3.1. Where is the Java code?</h3>
 <p>
           Because we are based on Apache Cocoon, a lot of the functionality is
@@ -1316,7 +1315,7 @@
           Locationmap and Dispatcher. There is also Java code for some plugins
           with specialised purpose, e.g. PhotoGallery.
         </p>
-<a name="N10370"></a><a name="populate-cache"></a>
+<a name="N1036F"></a><a name="populate-cache"></a>
 <h3 class="underlined_5">3.2. How to enhance the responsiveness of the cache?</h3>
 <p>
           Apache Cocoon has a sophisticated cache. When running Forrest in
@@ -1341,7 +1340,7 @@
           proxy server, e.g. Apache HTTP Server as a frontend. See
           <a href="http://wiki.apache.org/cocoon/ApacheModProxy">CocoonAndApacheModProxy</a>.
         </p>
-<a name="N1038A"></a><a name="proxy_config"></a>
+<a name="N10389"></a><a name="proxy_config"></a>
 <h3 class="underlined_5">3.3. I'm behind a proxy and it's preventing Plugins from being downloaded, what should I
         do?</h3>
 <p>
@@ -1362,7 +1361,7 @@
           <span class="codefrag">${user.home}/forrest.properties</span> !
         </div>
 </div>
-<a name="N103AE"></a><a name="CVS_revison_tags"></a>
+<a name="N103AD"></a><a name="CVS_revison_tags"></a>
 <h3 class="underlined_5">3.4. How can I generate html-pages to show the Revision tag of CVS or SVN?</h3>
 <p>
           If you have:<span class="codefrag">&lt;version&gt;$Revision: 1.30
@@ -1379,7 +1378,7 @@
           When using Subversion, remember to set the relevant svn:keywords
           properties.
         </p>
-<a name="N103C3"></a><a name="cli-xconf"></a>
+<a name="N103C2"></a><a name="cli-xconf"></a>
 <h3 class="underlined_5">3.5.  How to control the processing of URIs by Cocoon, e.g. exclude certain URIs, include
         other additional ones. </h3>
 <p>
@@ -1438,7 +1437,7 @@
           which explains how to include non-linked extra documents to the processing
           using the Cocoon CLI.
         </p>
-<a name="N10407"></a><a name="ignoring_javadocs"></a>
+<a name="N10406"></a><a name="ignoring_javadocs"></a>
 <h3 class="underlined_5">3.6.  How do I stop Forrest breaking on links to external files that may not exist, like
         javadocs? </h3>
 <p>
@@ -1446,7 +1445,7 @@
           <span class="codefrag">cli.xconf</span> </a> Cocoon config file, and defining
           patterns for URLs to exclude.
         </p>
-<a name="N10416"></a><a name="claimed_patterns"></a>
+<a name="N10415"></a><a name="claimed_patterns"></a>
 <h3 class="underlined_5">3.7. Some of my files are not being processed because they use common filenames. </h3>
 <p>
           Certain patterns are claimed by the default sitemaps for special
@@ -1460,7 +1459,7 @@
           of Forrest we will attempt to deal with this issue
           (<a href="http://issues.apache.org/jira/browse/FOR-217">FOR-217</a>).
         </p>
-<a name="N10428"></a><a name="build_msg_a"></a>
+<a name="N10427"></a><a name="build_msg_a"></a>
 <h3 class="underlined_5">3.8. What do the symbols and numbers mean when Forrest lists each document that it has
         built? </h3>
 <p>
@@ -1489,7 +1488,7 @@
 <li>Column 5 is the page size.</li>
         
 </ul>
-<a name="N10446"></a><a name="headless_operation"></a>
+<a name="N10445"></a><a name="headless_operation"></a>
 <h3 class="underlined_5">3.9.  When generating PNG images from SVG, I get an error: Can't connect to X11 window
         server using ':0.0' as the value of the DISPLAY variable. </h3>
 <p>
@@ -1503,7 +1502,7 @@
           <a href="http://cocoon.apache.org/2.1/faq/faq-configure-environment.html">Cocoon
           FAQ</a>.
         </p>
-<a name="N10462"></a><a name="project-logo-svg"></a>
+<a name="N10461"></a><a name="project-logo-svg"></a>
 <h3 class="underlined_5">3.10.  
         The project logo that is generated from SVG is truncating my project name.
       </h3>
@@ -1519,7 +1518,7 @@
           details see <a href="http://www.w3.org/Graphics/SVG/">SVG</a>
           resources.
         </p>
-<a name="N1047A"></a><a name="catalog"></a>
+<a name="N10479"></a><a name="catalog"></a>
 <h3 class="underlined_5">3.11.  How do i configure my favourite XML editor or parser to find the local Forrest
         DTDs? </h3>
 <p>
@@ -1527,24 +1526,24 @@
           <a href="../docs_0_90/catalog.html">Using Catalog Entity Resolver for local
           DTDs</a>.
         </p>
-<a name="N10486"></a><a name="project-dtd"></a>
+<a name="N10485"></a><a name="project-dtd"></a>
 <h3 class="underlined_5">3.12. How to configure the Catalog Entity Resolver to use my own local project DTDs?</h3>
 <p>
           See <a href="../docs_0_90/your-project.html#new_dtd">Using Forrest</a> for
           configuration guidance.
         </p>
-<a name="N10492"></a><a name="local-catalog"></a>
+<a name="N10491"></a><a name="local-catalog"></a>
 <h3 class="underlined_5">3.13. We need an additional system-wide catalog to share DTDs between projects</h3>
 <p>
           See <a href="../docs_0_90/validation.html#catalog">Using Forrest</a> for
           configuration guidance.
         </p>
-<a name="N1049E"></a><a name="debug-catalog"></a>
+<a name="N1049D"></a><a name="debug-catalog"></a>
 <h3 class="underlined_5">3.14. How to debug the Catalog Entity Resolver and local DTDs?</h3>
 <p>
           See <a href="../docs_0_90/validation.html#debug-catalog">XML validation</a>.
         </p>
-<a name="N104AA"></a><a name="skin"></a>
+<a name="N104A9"></a><a name="skin"></a>
 <h3 class="underlined_5">3.15.  How to make the site look better and change its skin? </h3>
 <p>
           There are <a href="../docs_0_90/your-project.html#skins">default skins</a> provided, which
@@ -1558,7 +1557,7 @@
           skins. Some projects may have special needs and can define their
           <a href="../docs_0_90/your-project.html#new_skin">own skin</a>.
         </p>
-<a name="N104C1"></a><a name="xsp"></a>
+<a name="N104C0"></a><a name="xsp"></a>
 <h3 class="underlined_5">3.16. How do I enable XSP processing?</h3>
 <p>
           First consider whether your needs would be better met by Cocoon
@@ -1617,7 +1616,7 @@
           <a href="http://wiki.apache.org/cocoon/AddingXSPToForrest">AddingXSPToForrest</a>
           Wiki page.
         </p>
-<a name="N104F8"></a><a name="breadcrumbs"></a>
+<a name="N104F7"></a><a name="breadcrumbs"></a>
 <h3 class="underlined_5">3.17. How do breadcrumbs work? Why don't they work locally?</h3>
 <p>
           Breadcrumbs begin with up to three URLs specified in
@@ -1638,7 +1637,7 @@
           there is no domain and so there will be no extra breadcrumbs, only the
           ones that are specified in <span class="codefrag">skinconf.xml</span>.
         </p>
-<a name="N1050D"></a><a name="run_port"></a>
+<a name="N1050C"></a><a name="run_port"></a>
 <h3 class="underlined_5">3.18. How do I make forrest run listen on a different port?</h3>
 <p>
           
@@ -1651,7 +1650,7 @@
           do <span class="codefrag">forrest run</span>
         
 </p>
-<a name="N10521"></a><a name="debugging"></a>
+<a name="N10520"></a><a name="debugging"></a>
 <h3 class="underlined_5">3.19. Can I run Forrest with Java debugging turned on?</h3>
 <p>
           If you use an IDE like Eclipse and want to debug java code in Forrest
@@ -1662,7 +1661,7 @@
           <span class="codefrag">forrest.properties</span> file. Don't forget to ensure the
           property is uncommented in that file.
         </p>
-<a name="N10532"></a><a name="checksums"></a>
+<a name="N10531"></a><a name="checksums"></a>
 <h3 class="underlined_5">3.20. How do I enable Cocoon's document checksum feature?</h3>
 <p>
           Why might you want to do this? There is really no effect on Cocoon
@@ -1690,7 +1689,7 @@
           <a href="#cli-xconf">Cocoon cli.xconf</a>) or use the default
           installation-wide cli.xconf file.
         </p>
-<a name="N1054E"></a><a name="sitemap-entities"></a>
+<a name="N1054D"></a><a name="sitemap-entities"></a>
 <h3 class="underlined_5">3.21. How to configure some Cocoon sitemap components, e.g. output html encoding or doctype?</h3>
 <p>
           The core Cocoon components are defined in the
@@ -1714,10 +1713,10 @@
           Re-start Forrest.
         </p>
 </div>
-<a name="N10568"></a><a name="old_faqs"></a>
+<a name="N10567"></a><a name="old_faqs"></a>
 <h2 class="underlined_10">4. Older version: 0.6</h2>
 <div class="section">
-<a name="N1056C"></a><a name="old_claimed_patterns"></a>
+<a name="N1056B"></a><a name="old_claimed_patterns"></a>
 <h3 class="underlined_5">4.1. Some of my files are not being processed because they use common filenames. </h3>
 <p>
           Certain patterns are claimed by the default sitemaps for special
@@ -1732,10 +1731,10 @@
           (<a href="http://issues.apache.org/jira/browse/FOR-217">FOR-217</a>).
         </p>
 </div>
-<a name="N1057E"></a><a name="general"></a>
+<a name="N1057D"></a><a name="general"></a>
 <h2 class="underlined_10">5. General</h2>
 <div class="section">
-<a name="N10582"></a><a name="generating_menus"></a>
+<a name="N10581"></a><a name="generating_menus"></a>
 <h3 class="underlined_5">5.1. What is the relationship between site.xml and book.xml? </h3>
 <p>
           One <span class="codefrag">site.xml</span> file in your project root can replace all the book.xml files
@@ -1747,7 +1746,7 @@
           where <span class="codefrag">site.xml</span>-generated menus aren't appropriate. See
           <a href="../docs_0_90/linking.html">Menus and Linking</a>.
         </p>
-<a name="N1059D"></a><a name="docbook"></a>
+<a name="N1059C"></a><a name="docbook"></a>
 <h3 class="underlined_5">5.2.  How do I use DocBook as the XML documentation format? </h3>
 <p>
           There are two ways. Forrest has a <span class="codefrag">simplifiedDocbook</span>
@@ -1857,7 +1856,7 @@
           <a href="../docs_0_90/your-project.html#new_dtd">Using Forrest</a> for
           configuration guidance.
         </p>
-<a name="N105D6"></a><a name="version"></a>
+<a name="N105D5"></a><a name="version"></a>
 <h3 class="underlined_5">5.3.  How to report which version of Forrest is being used and the properties that are
         set? </h3>
 <p>
@@ -1869,7 +1868,7 @@
           forrest.properties file and watch the build messages. Doing
           <span class="codefrag">'forrest -v'</span> will provide verbose build messages.
         </p>
-<a name="N105EA"></a><a name="logs"></a>
+<a name="N105E9"></a><a name="logs"></a>
 <h3 class="underlined_5">5.4.  Where are the log files to find more infomation about errors? </h3>
 <p>
           The logfiles are at <span class="codefrag">build/webapp/WEB-INF/logs/</span>
@@ -1891,7 +1890,7 @@
           Doing <span class="codefrag">'forrest -v'</span> will provide verbose build messages to
           the standard output.
         </p>
-<a name="N1060E"></a><a name="how_can_I_help"></a>
+<a name="N1060D"></a><a name="how_can_I_help"></a>
 <h3 class="underlined_5">5.5.  How to help? </h3>
 <p>
           Join one of the Forrest project <a href="../mail-lists.html">mailing
@@ -1900,7 +1899,7 @@
           newcomers&mdash;often, close proximity blinds software developers to
           faults that are obvious to everyone else. Don't be shy!
         </p>
-<a name="N1061A"></a><a name="patch"></a>
+<a name="N10619"></a><a name="patch"></a>
 <h3 class="underlined_5">5.6.  How to contribute a patch? </h3>
 <p>
           Please send all contributions via our <a href="../issues.html">issue
@@ -1914,7 +1913,7 @@
           <a href="../issues.html">issue tracker</a> before diving
           in.
         </p>
-<a name="N10635"></a><a name="jobs"></a>
+<a name="N10634"></a><a name="jobs"></a>
 <h3 class="underlined_5">5.7.  How can job positions be advertised? </h3>
 <p>
           Employers can send notices about employment opportunities. There is a
@@ -1933,7 +1932,7 @@
           (<a href="http://www.apache.org/licenses/">CCLA</a>) with The
           Apache Software Foundation.
         </p>
-<a name="N10648"></a><a name="press"></a>
+<a name="N10647"></a><a name="press"></a>
 <h3 class="underlined_5">5.8. Is there a press kit? Who can journalists contact?</h3>
 <p>
          Press enquiries should be co-ordinated through the ASF Public Relations Committee (PRC).
@@ -1952,7 +1951,7 @@
           are available.
           Unfortunately the logo is only available as PNG.
         </p>
-<a name="N1066B"></a><a name="security"></a>
+<a name="N1066A"></a><a name="security"></a>
 <h3 class="underlined_5">5.9. How to report a security issue?</h3>
 <p>
          Security and vulnerability issues are co-ordinated through the

Modified: forrest/site/docs_0_90/faq.xml
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_90/faq.xml?rev=813336&r1=813335&r2=813336&view=diff
==============================================================================
--- forrest/site/docs_0_90/faq.xml (original)
+++ forrest/site/docs_0_90/faq.xml Thu Sep 10 09:55:21 2009
@@ -565,18 +565,17 @@
         </p>
       </section><section id="i18n"><title>2.20. How can I internationalise (i18n) my content?</title>
         <p>
-          The i18n features of Forrest are still under development (as of 0.7)
-          however there are some features available. For example, navigation
-          menus can be i18n'd (see fresh-site for an example). Currently,
-          <link href="http://issues.apache.org/jira/browse/FOR-506">work is
-          underway</link> to i18n skins
+          For example, navigation
+          menus can be internationalized and different content can be served.
         </p>
         <p>
-          All internationalistation of tokens in, for example, the skins and the
-          menus, is carried out by the
+          There is an example to demonstrate and explain the facilities.
+          See a 'forrest seed-sample' site.
+        </p>
+        <p>
+          All internationalisation of tokens is carried out by the
           <link href="http://cocoon.apache.org/2.1/userdocs/i18nTransformer.html">Cocoon
-          i18n Transformer</link>. You can see an example of how it works in the
-          above linked issue.
+          i18n Transformer</link>.
         </p>
       </section><section id="rawHTML"><title>2.21. How can I include HTML content that is not to be skinned by Forrest?</title>
         <p>

Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewvc/forrest/site/forrest-issues.html?rev=813336&r1=813335&r2=813336&view=diff
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Thu Sep 10 09:55:21 2009
@@ -202,9 +202,6 @@
 <a href="#%5BFOR-796%5D+Merge+all+view%2Fdispatcher+work+into+org.apache.forrest.plugin.internal.dispatcher+and+org.apache.forrest.themes.core">[FOR-796] Merge all view/dispatcher work into org.apache.forrest.plugin.internal.dispatcher and org.apache.forrest.themes.core</a>
 </li>
 <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-855%5D+verify+the+license+situation+prior+to+each+release">[FOR-855] verify the license situation prior to each release</a>
 </li>
 <li>
@@ -220,6 +217,12 @@
 <a href="#%5BFOR-1108%5D+Dispatcher%2C+Cocoon+2.1+and+Windows">[FOR-1108] Dispatcher, Cocoon 2.1 and Windows</a>
 </li>
 <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-1176%5D+enable+plugins+to+utilise+stylesheets+from+exslt.org">[FOR-1176] enable plugins to utilise stylesheets from exslt.org</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>
@@ -267,9 +270,6 @@
 <li>
 <a href="#%5BFOR-785%5D+plugins%2F*%2Fskinconf.xml+does+not+validate+since+using+entity+to+ease+management">[FOR-785] plugins/*/skinconf.xml does not validate since using entity to ease management</a>
 </li>
-<li>
-<a href="#%5BFOR-1073%5D+link+elements+with+no+href+are+created+by+html-to-document.xsl+for+a%2Fname">[FOR-1073] link elements with no href are created by html-to-document.xsl for a/name</a>
-</li>
 </ul>
 </div>
 </div>
@@ -345,21 +345,7 @@
 </p>
 <p>This is the global issue to keep track on the merging effort</p>
 </div>
-<a name="N10029"></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.&lt;br/&gt;
-&lt;br/&gt;
-Possibly &lt;a href="http://issues.apache.org/jira/browse/COCOON-1574" title="Memory Leak with XMLFileModule"&gt;COCOON-1574&lt;/a&gt; &amp;quot;Memory Leak with XMLFileModule&amp;quot;.&lt;br/&gt;
-&lt;br/&gt;
-Does someone have the tools to run some diagnostics?&lt;br/&gt;
-&lt;br/&gt;
-(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="N10035"></a><a name="%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release"></a>
+<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>
 <div class="section">
 <p>
@@ -375,7 +361,7 @@
 &lt;br/&gt;
 C) Remove any author tags.</p>
 </div>
-<a name="N10041"></a><a name="%5BFOR-911%5D+decide+content+of+release"></a>
+<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>
 <div class="section">
 <p>
@@ -387,7 +373,7 @@
 &amp;nbsp;content of release [was: Re: review list of scheduled issues for 0.8 release]&lt;br/&gt;
 &amp;nbsp;&lt;a href="http://marc.theaimsgroup.com/?t=115257903800001"&gt;http://marc.theaimsgroup.com/?t=115257903800001&lt;/a&gt;</p>
 </div>
-<a name="N1004D"></a><a name="%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc"></a>
+<a name="N10041"></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>
@@ -395,7 +381,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 &lt;a href="http://issues.apache.org/jira/browse/FOR-865" title="Add missing entries to status.xml to generate the changes list"&gt;&lt;strike&gt;FOR-865&lt;/strike&gt;&lt;/a&gt; &amp;quot;Add missing entries to status.xml to generate the changes list&amp;quot;.</p>
 </div>
-<a name="N10059"></a><a name="%5BFOR-812%5D+Remove+dependency+of+projectInfo+on+skinconf.xml"></a>
+<a name="N1004D"></a><a name="%5BFOR-812%5D+Remove+dependency+of+projectInfo+on+skinconf.xml"></a>
 <h2 class="underlined_10">[FOR-812] Remove dependency of projectInfo on skinconf.xml</h2>
 <div class="section">
 <p>
@@ -405,7 +391,7 @@
 &lt;br/&gt;
 We should chage the projectInfo plugin so that this value is provided by a plugin property.</p>
 </div>
-<a name="N10065"></a><a name="%5BFOR-1108%5D+Dispatcher%2C+Cocoon+2.1+and+Windows"></a>
+<a name="N10059"></a><a name="%5BFOR-1108%5D+Dispatcher%2C+Cocoon+2.1+and+Windows"></a>
 <h2 class="underlined_10">[FOR-1108] Dispatcher, Cocoon 2.1 and Windows</h2>
 <div class="section">
 <p>
@@ -413,7 +399,29 @@
 </p>
 <p>Since the update to Cocoon 2.1 Forrest and Dispatcher have broken on windows.</p>
 </div>
-<a name="N10071"></a><a name="%5BFOR-572%5D+run+a+memory+profiler+while+forrest+is+operating"></a>
+<a name="N10065"></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.&lt;br/&gt;
+&lt;br/&gt;
+Possibly &lt;a href="http://issues.apache.org/jira/browse/COCOON-1574" title="Memory Leak with XMLFileModule"&gt;COCOON-1574&lt;/a&gt; &amp;quot;Memory Leak with XMLFileModule&amp;quot;.&lt;br/&gt;
+&lt;br/&gt;
+Does someone have the tools to run some diagnostics?&lt;br/&gt;
+&lt;br/&gt;
+(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="N10071"></a><a name="%5BFOR-1176%5D+enable+plugins+to+utilise+stylesheets+from+exslt.org"></a>
+<h2 class="underlined_10">[FOR-1176] enable plugins to utilise stylesheets from exslt.org</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-1176">http://issues.apache.org/jira/browse/FOR-1176</a>
+</p>
+<p>Various plugins (e.g. &amp;quot;input.baetle&amp;quot;) want to use selected stylesheets from exslt.org</p>
+</div>
+<a name="N1007D"></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>
@@ -421,7 +429,7 @@
 </p>
 <p>We need to run a memory profiler while forrest is operating.</p>
 </div>
-<a name="N1007D"></a><a name="%5BFOR-986%5D+Dispatcher+war+fails+to+build+if+no+skinconf.xml+is+in+place"></a>
+<a name="N10089"></a><a name="%5BFOR-986%5D+Dispatcher+war+fails+to+build+if+no+skinconf.xml+is+in+place"></a>
 <h2 class="underlined_10">[FOR-986] Dispatcher war fails to build if no skinconf.xml is in place</h2>
 <div class="section">
 <p>
@@ -435,7 +443,7 @@
 &lt;br/&gt;
 To work around this issue just put a skinconf.xml in place</p>
 </div>
-<a name="N10089"></a><a name="%5BFOR-588%5D+Design+new+configuration+system"></a>
+<a name="N10095"></a><a name="%5BFOR-588%5D+Design+new+configuration+system"></a>
 <h2 class="underlined_10">[FOR-588] Design new configuration system</h2>
 <div class="section">
 <p>
@@ -443,7 +451,7 @@
 </p>
 <p>We need a new config system for Forrest for various reasons: the initial config system was known to be limited; to enable the specification of multiple Forrest sites within a single instance of Forrest; to accommodate the changes brought about by forrest:views, themes, and plugins.</p>
 </div>
-<a name="N10095"></a><a name="%5BFOR-970%5D+Add+a+way+to+have+plugin+specific+resources%2C+such+as+its+own+CSS+styling%2C+independent+of+skin+or+theme"></a>
+<a name="N100A1"></a><a name="%5BFOR-970%5D+Add+a+way+to+have+plugin+specific+resources%2C+such+as+its+own+CSS+styling%2C+independent+of+skin+or+theme"></a>
 <h2 class="underlined_10">[FOR-970] Add a way to have plugin specific resources, such as its own CSS styling, independent of skin or theme</h2>
 <div class="section">
 <p>
@@ -452,7 +460,7 @@
 <p>It would be nice if plugins could be a little more independent of core skins and themes for plugin specific styling.&lt;br/&gt;
 This could be CSS, or something else, I have only identified CSS needs at present.</p>
 </div>
-<a name="N100A1"></a><a name="%5BFOR-1081%5D+Create+example+document%28s%29+with+all+common+and+pelt+contracts+enabled+and+working."></a>
+<a name="N100AD"></a><a name="%5BFOR-1081%5D+Create+example+document%28s%29+with+all+common+and+pelt+contracts+enabled+and+working."></a>
 <h2 class="underlined_10">[FOR-1081] Create example document(s) with all common and pelt contracts enabled and working.</h2>
 <div class="section">
 <p>
@@ -461,7 +469,7 @@
 <p>All available contracts should be enabled in Panels and working so that they may be used as examples and also as a test to ensure they work; and as a warning when they don't.&lt;br/&gt;
 So , in the style of document-v20 this should be created in seed-sample2 so that forrestbot can let us know when any contracts break.</p>
 </div>
-<a name="N100AD"></a><a name="%5BFOR-388%5D+Use+plugins+in-place+if+src+available"></a>
+<a name="N100B9"></a><a name="%5BFOR-388%5D+Use+plugins+in-place+if+src+available"></a>
 <h2 class="underlined_10">[FOR-388] Use plugins in-place if src available</h2>
 <div class="section">
 <p>
@@ -473,7 +481,7 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N100B9"></a><a name="%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links"></a>
+<a name="N100C5"></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>
@@ -483,7 +491,7 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N100C5"></a><a name="%5BFOR-217%5D+Certain+patterns+are+claimed+by+the+default+sitemaps"></a>
+<a name="N100D1"></a><a name="%5BFOR-217%5D+Certain+patterns+are+claimed+by+the+default+sitemaps"></a>
 <h2 class="underlined_10">[FOR-217] Certain patterns are claimed by the default sitemaps</h2>
 <div class="section">
 <p>
@@ -492,7 +500,7 @@
 <p>Users are prevented from using certain filenames because those patterns are claimed by the default sitemaps for special processing. These include: site, changes, todo, faq, images, my-images, skinconf, cprofile&lt;br/&gt;
 </p>
 </div>
-<a name="N100D1"></a><a name="%5BFOR-560%5D+Remove+duplicate+jars+from+eclipse+plugins"></a>
+<a name="N100DD"></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>
@@ -500,7 +508,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-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>
@@ -510,7 +518,7 @@
 &lt;br/&gt;
 This is most likely a side-effect of the workaround for issue &lt;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."&gt;FOR-675&lt;/a&gt;</p>
 </div>
-<a name="N100E9"></a><a name="%5BFOR-676%5D+logkit.xconf+has+no+effect+on+configuration+when+in+commandline+mode"></a>
+<a name="N100F5"></a><a name="%5BFOR-676%5D+logkit.xconf+has+no+effect+on+configuration+when+in+commandline+mode"></a>
 <h2 class="underlined_10">[FOR-676] logkit.xconf has no effect on configuration when in commandline mode</h2>
 <div class="section">
 <p>
@@ -518,7 +526,7 @@
 </p>
 <p>Raising loglevels in main/webapp/WEB-INF/logkit.xconf has no effect when doing 'forrest'. All okay when doing 'forrest run'.</p>
 </div>
-<a name="N100F5"></a><a name="%5BFOR-675%5D+upgrading+to+commons-jxpath-1.2.jar+causes+failures+with+linkrewriter+protocols+site%3A+etc."></a>
+<a name="N10101"></a><a name="%5BFOR-675%5D+upgrading+to+commons-jxpath-1.2.jar+causes+failures+with+linkrewriter+protocols+site%3A+etc."></a>
 <h2 class="underlined_10">[FOR-675] upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc.</h2>
 <div class="section">
 <p>
@@ -526,7 +534,7 @@
 </p>
 <p>upgrading from commons-jxpath-20030909.jar to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc. This happens in both modes: 'forret run' and 'forrest'.</p>
 </div>
-<a name="N10101"></a><a name="%5BFOR-677%5D+leading+slash+in+gathered+URIs+causes+double+the+number+of+links+to+be+processed"></a>
+<a name="N1010D"></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>
@@ -540,7 +548,7 @@
 &lt;br/&gt;
 However, we do have a sitemap transformer to &amp;quot;relativize&amp;quot; and &amp;quot;absolutize&amp;quot; the links. Should it always trim the leading slash? Or are there cases where that should not happen, so cannot generalise?</p>
 </div>
-<a name="N1010D"></a><a name="%5BFOR-699%5D+Beginner+HowTos+for+installing+Forrest"></a>
+<a name="N10119"></a><a name="%5BFOR-699%5D+Beginner+HowTos+for+installing+Forrest"></a>
 <h2 class="underlined_10">[FOR-699] Beginner HowTos for installing Forrest</h2>
 <div class="section">
 <p>
@@ -548,7 +556,7 @@
 </p>
 <p>These are a whole group of HowTos that I wrote for my local users (probably a tutorial would be a better format).  They are not complete, nor tidied at this point, but they cover a lot of basic step-by-step stuff specifically geared towards Linux with Gnome desktop and Windows XP.  Figured I would put them out there so we can pull out bits we may want to use.</p>
 </div>
-<a name="N10119"></a><a name="%5BFOR-705%5D+Target+of+LocationMap+rewriteDemo+causes+build+failure+when+target+not+available"></a>
+<a name="N10125"></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>
@@ -566,7 +574,7 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N10125"></a><a name="%5BFOR-785%5D+plugins%2F*%2Fskinconf.xml+does+not+validate+since+using+entity+to+ease+management"></a>
+<a name="N10131"></a><a name="%5BFOR-785%5D+plugins%2F*%2Fskinconf.xml+does+not+validate+since+using+entity+to+ease+management"></a>
 <h2 class="underlined_10">[FOR-785] plugins/*/skinconf.xml does not validate since using entity to ease management</h2>
 <div class="section">
 <p>
@@ -576,17 +584,6 @@
 &lt;br/&gt;
 Okay, i admit it ... forgot to do 'build test' :-) and it doesn't validate. The DTD insists on having the elements in a specific order.</p>
 </div>
-<a name="N10131"></a><a name="%5BFOR-1073%5D+link+elements+with+no+href+are+created+by+html-to-document.xsl+for+a%2Fname"></a>
-<h2 class="underlined_10">[FOR-1073] link elements with no href are created by html-to-document.xsl for a/name</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-1073">http://issues.apache.org/jira/browse/FOR-1073</a>
-</p>
-<p>In &lt;a href="http://issues.apache.org/jira/browse/FOR-1072" title="[PATCH] Bugfixes and improvements for PDF output plugin"&gt;&lt;strike&gt;FOR-1072&lt;/strike&gt;&lt;/a&gt; Jeremias said:&lt;br/&gt;
-&amp;quot;Filtered out link elements with no href (which are created by html-to-document.xsl for &amp;quot;&amp;lt;a name=...&amp;quot;). Forrest 0.7 didn't generate them as links at all but trunk does. Maybe that's wrong in the first place. &amp;quot;&lt;br/&gt;
-&lt;br/&gt;
-There was also a mention of it previously on the dev list surrounding the recent FOP update branch work.</p>
-</div>
 </div>
 <!--+
     |end content

Modified: forrest/site/guidelines.html
URL: http://svn.apache.org/viewvc/forrest/site/guidelines.html?rev=813336&r1=813335&r2=813336&view=diff
==============================================================================
--- forrest/site/guidelines.html (original)
+++ forrest/site/guidelines.html Thu Sep 10 09:55:21 2009
@@ -677,7 +677,7 @@
           
 <tr>
             
-<td colspan="1" rowspan="1"><strong>Lazy majority</strong>
+<td colspan="1" rowspan="1"><strong>Lazy majority (majority consensus)</strong>
             </td>
             <td colspan="1" rowspan="1">
             A lazy majority vote requires 3 binding +1 votes and more binding +1

Modified: forrest/site/procedures/release/How_to_release.html
URL: http://svn.apache.org/viewvc/forrest/site/procedures/release/How_to_release.html?rev=813336&r1=813335&r2=813336&view=diff
==============================================================================
--- forrest/site/procedures/release/How_to_release.html (original)
+++ forrest/site/procedures/release/How_to_release.html Thu Sep 10 09:55:21 2009
@@ -535,7 +535,9 @@
             If you have never done a release before or need to refresh your
             memory, read all about Apache releases in general at
             <a href="http://www.apache.org/dev/#releases">http://www.apache.org/dev/#releases</a>
-            (note that these documents change often). Make sure any assistants
+            and
+            <a href="http://incubator.apache.org/guides/releasemanagement.html">Apache Incubator</a>.
+            Note that these documents change often. Make sure any assistants
             have read and understood this as well.
           </p>
 </li>
@@ -581,7 +583,7 @@
 </ul>
 </div>
     
-<a name="N100FE"></a><a name="PrepRelPlan"></a>
+<a name="N10102"></a><a name="PrepRelPlan"></a>
 <h2 class="underlined_10">Preparing the Release Plan</h2>
 <div class="section">
 <p>
@@ -635,7 +637,7 @@
 </div>
 </div>
     
-<a name="N1013D"></a><a name="PrepCodeBase"></a>
+<a name="N10141"></a><a name="PrepCodeBase"></a>
 <h2 class="underlined_10">Preparing the code base</h2>
 <div class="section">
 <p>
@@ -728,7 +730,7 @@
 </ol>
 </div>
     
-<a name="N10183"></a><a name="PrepTrunk"></a>
+<a name="N10187"></a><a name="PrepTrunk"></a>
 <h2 class="underlined_10">Preparing your working copy of SVN trunk</h2>
 <div class="section">
 <div class="fixme">
@@ -784,7 +786,7 @@
 </ol>
 </div>
     
-<a name="N101B1"></a><a name="PrepDistSvn"></a>
+<a name="N101B5"></a><a name="PrepDistSvn"></a>
 <h2 class="underlined_10">Preparing the "dist" SVN</h2>
 <div class="section">
 <p>
@@ -804,7 +806,7 @@
       </p>
 </div>
     
-<a name="N101C5"></a><a name="adjustDocs"></a>
+<a name="N101C9"></a><a name="adjustDocs"></a>
 <h2 class="underlined_10">Preparing docs for next release cycle</h2>
 <div class="section">
 <p>
@@ -983,7 +985,7 @@
 </div>
 </div>
     
-<a name="N10250"></a><a name="BuildDist"></a>
+<a name="N10254"></a><a name="BuildDist"></a>
 <h2 class="underlined_10">Building the release candidate packages</h2>
 <div class="section">
 <p>
@@ -1273,7 +1275,7 @@
 </ol>
 </div>
     
-<a name="N10310"></a><a name="vote"></a>
+<a name="N10314"></a><a name="vote"></a>
 <h2 class="underlined_10">Testing the release candidate and voting</h2>
 <div class="section">
 <p>
@@ -1342,7 +1344,7 @@
 </div>
 </div>
     
-<a name="N1034C"></a><a name="FinalRel"></a>
+<a name="N10350"></a><a name="FinalRel"></a>
 <h2 class="underlined_10">Finalizing the release</h2>
 <div class="section">
 <p>
@@ -1439,7 +1441,7 @@
 </ol>
 </div>
     
-<a name="N10391"></a><a name="prepSite"></a>
+<a name="N10395"></a><a name="prepSite"></a>
 <h2 class="underlined_10">Prepare the site-author docs for next development phase</h2>
 <div class="section">
 <div class="note">
@@ -1514,6 +1516,10 @@
         
 <li>Edit version numbers in tools/forrestbar</li>
         
+<li>Increment the version numbers in the head of the xml source of this
+          "How_to_release" document. These are xml entities which display the
+          various version numbers in this document.</li>
+        
 <li>
 <p>
             Update the .htaccess file to redirect /docs/dev/ to the next
@@ -1543,7 +1549,7 @@
 </ul>
 </div>
     
-<a name="N103E5"></a><a name="UploadAndAnnounce"></a>
+<a name="N103EC"></a><a name="UploadAndAnnounce"></a>
 <h2 class="underlined_10">Upload and announcement</h2>
 <div class="section">
 <p>
@@ -1721,7 +1727,7 @@
 </ol>
 </div>
     
-<a name="N104A3"></a><a name="cleanup"></a>
+<a name="N104AA"></a><a name="cleanup"></a>
 <h2 class="underlined_10">Cleanup</h2>
 <div class="section">
 <ol>
@@ -1788,7 +1794,7 @@
 </ol>
 </div>
     
-<a name="N104D5"></a><a name="conclusion"></a>
+<a name="N104DC"></a><a name="conclusion"></a>
 <h2 class="underlined_10">Conclusion</h2>
 <div class="section">
 <p>

Modified: forrest/site/tasks.html
URL: http://svn.apache.org/viewvc/forrest/site/tasks.html?rev=813336&r1=813335&r2=813336&view=diff
==============================================================================
--- forrest/site/tasks.html (original)
+++ forrest/site/tasks.html Thu Sep 10 09:55:21 2009
@@ -319,7 +319,7 @@
         by enhancing the task documentation.
       </p>
 <p>
-        Most of the tasks (except of course the Developer role) can only be
+        Most of the tasks (except of course the Developer tasks) can only be
         carried out by PMC members because commit access is required.
       </p>
 </div>
@@ -353,8 +353,8 @@
         
 </p>
 <p>
-          Only one person can do this role, although other people can assist.
-          There is a lot of knowledge invested in this role. Document it as much
+          Only one person can do this task, although other people can assist.
+          There is a lot of knowledge invested in this RM role. Document it as much
           as possible.
         </p>
 <a name="N10060"></a><a name="forrest-friday-coordination"></a>
@@ -443,27 +443,46 @@
 <h3 class="underlined_5">Legal Monitoring</h3>
 <p>
           Regularly run a script which verifies and inserts missing license
-          headers to source files.
+          headers to source files. Review the output and fix issues.
+          For example:
+          <a href="https://svn.apache.org/repos/private/committers/relicense/src/perl/">committers/relicense/src/perl/</a>
+          and other tools at
+          <a href="https://svn.apache.org/repos/private/committers/tools/">committers/tools/</a>
+          and
+          <a href="http://incubator.apache.org/rat/">Apache RAT</a> (currently in Incubator)
+          and some other suggestions at
+          <a href="http://labs.apache.org/">Apache Labs</a>.
+          See also some tips in
+          <a href="https://issues.apache.org/jira/browse/FOR-855">FOR-855</a>
+          and
+          <a href="https://issues.apache.org/jira/browse/FOR-123">FOR-123</a>.
         </p>
 <p>
           Regularly ensure that there are appropriate matching licenses to
           accompany each supporting product that we redistribute.
+          (Use the filename pattern: product-version[.-]license.txt or uppercase.)
+        </p>
+<p>
+          For each such license, also ensure that it is referred to in
+          $FORREST_HOME/LICENSE.txt file. If their license required attribution,
+          then add to $FORREST_HOME/NOTICE.txt file. Also replicate any NOTICE
+          which accompanies a supporting product.
+          See <a href="https://issues.apache.org/jira/browse/FOR-857">FOR-857</a>.
+        </p>
+<p>
+          See some guidelines at
+          <a href="http://www.apache.org/dev/#licenses">ASF Legal</a>.
         </p>
 <p>
           This should have continual oversight by the PMC as a whole, but the
           monitoring is something that needs to be done regularly, and
           definitely prior to each release.
         </p>
-<p>
-          There are already some Perl scripts and other tools in the
-          "<a href="https://svn.apache.org/repos/private/committers">committers</a>"
-          SVN in the "tools" and "relicense/src/perl" directories.
-        </p>
-<a name="N100DF"></a><a name="developer"></a>
+<a name="N100FE"></a><a name="developer"></a>
 <h3 class="underlined_5">Developer</h3>
 <p>
-          The above tasks are only for PMC Members. How can the Developers be
-          involved? That is easy: do the Developer Role.
+          The above tasks are only for PMC Members. How can any Developer be
+          involved? That is easy: do the Developer tasks.
         </p>
 <p>
           Help out with commenting on the Issue Tracker, fixing the issues,
@@ -473,7 +492,7 @@
 <p>
           This is incredibly valuable and will enable the project to grow. After
           time, you will probably be elected as Committer/PMC Member and when
-          comfortable, can take on one of the Project Management Roles.
+          comfortable, can take on one of the Project Management tasks.
         </p>
 </div>
   



Mime
View raw message