You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-svn@forrest.apache.org by cr...@apache.org on 2010/07/03 05:55:03 UTC
svn commit: r960152 - in /forrest/site: dtdx/document-v13.pdf
dtdx/document-v20.pdf forrest-issues.html gump.html
Author: crossley
Date: Sat Jul 3 03:55:02 2010
New Revision: 960152
URL: http://svn.apache.org/viewvc?rev=960152&view=rev
Log:
Publish from forrestbot
Modified:
forrest/site/dtdx/document-v13.pdf
forrest/site/dtdx/document-v20.pdf
forrest/site/forrest-issues.html
forrest/site/gump.html
Modified: forrest/site/dtdx/document-v13.pdf
URL: http://svn.apache.org/viewvc/forrest/site/dtdx/document-v13.pdf?rev=960152&r1=960151&r2=960152&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/dtdx/document-v20.pdf
URL: http://svn.apache.org/viewvc/forrest/site/dtdx/document-v20.pdf?rev=960152&r1=960151&r2=960152&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=960152&r1=960151&r2=960152&view=diff
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Sat Jul 3 03:55:02 2010
@@ -207,27 +207,18 @@ document.write("Last Published: " + docu
<a href="#%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc">[FOR-868] add relevant notes to the "Upgrading" xdoc</a>
</li>
<li>
-<a href="#%5BFOR-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-1108%5D+Dispatcher%2C+Cocoon+2.1+and+Windows">[FOR-1108] Dispatcher, Cocoon 2.1 and Windows</a>
</li>
<li>
-<a href="#%5BFOR-1199%5D+the+plugins+%22deploy%22+and+%22release%22+target+need+to+depend+on+%22publish%22+property">[FOR-1199] the plugins "deploy" and "release" target need to depend on "publish" property</a>
+<a href="#%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release">[FOR-855] verify the license situation prior to each release</a>
</li>
<li>
<a href="#%5BFOR-922%5D+update+all+docs+that+explain+sitemap+fragments">[FOR-922] update all docs that explain sitemap fragments</a>
</li>
<li>
-<a href="#%5BFOR-857%5D+append+license+files+to+the+top-level+LICENSE.txt">[FOR-857] append license files to the top-level LICENSE.txt</a>
-</li>
-<li>
<a href="#%5BFOR-1066%5D+Dispatcher+started+failing+on+seed+sample+site+recently+with+out-of-memory+error">[FOR-1066] Dispatcher started failing on seed sample site recently with out-of-memory error</a>
</li>
<li>
-<a href="#%5BFOR-1077%5D+new+CreationDate+causes+constant+differences+in+output+pdf+documents">[FOR-1077] new CreationDate causes constant differences in output pdf documents</a>
-</li>
-<li>
<a href="#%5BFOR-1184%5D+using+unreleased+code+for+some+supporting+products">[FOR-1184] using unreleased code for some supporting products</a>
</li>
<li>
@@ -261,10 +252,10 @@ document.write("Last Published: " + docu
<a href="#%5BFOR-1187%5D+upgraded+PDF+plugin+was+not+deployed+properly">[FOR-1187] upgraded PDF plugin was not deployed properly</a>
</li>
<li>
-<a href="#%5BFOR-1166%5D+Search+Button+is+misplaced+to+the+right+in+some+browsers+-+Pelt+Theme">[FOR-1166] Search Button is misplaced to the right in some browsers - Pelt Theme</a>
+<a href="#%5BFOR-1069%5D+add+notices+for+US+cryptographic+export+laws">[FOR-1069] add notices for US cryptographic export laws</a>
</li>
<li>
-<a href="#%5BFOR-1069%5D+add+notices+for+US+cryptographic+export+laws">[FOR-1069] add notices for US cryptographic export laws</a>
+<a href="#%5BFOR-1166%5D+Search+Button+is+misplaced+to+the+right+in+some+browsers+-+Pelt+Theme">[FOR-1166] Search Button is misplaced to the right in some browsers - Pelt Theme</a>
</li>
<li>
<a href="#%5BFOR-1168%5D+Sample+pages+that+fail+validation">[FOR-1168] Sample pages that fail validation</a>
@@ -273,7 +264,13 @@ document.write("Last Published: " + docu
<a href="#%5BFOR-1122%5D+Example+site+contentIntegration+currently+only+works+in+forrest+run+mode">[FOR-1122] Example site contentIntegration currently only works in forrest run mode</a>
</li>
<li>
-<a href="#%5BFOR-1200%5D+stop+re-generating+PDF+documents+on+Forrest+website">[FOR-1200] stop re-generating PDF documents on Forrest website</a>
+<a href="#%5BFOR-1077%5D+new+CreationDate+causes+constant+differences+in+output+pdf+documents">[FOR-1077] new CreationDate causes constant differences in output pdf documents</a>
+</li>
+<li>
+<a href="#%5BFOR-857%5D+append+license+files+to+the+top-level+LICENSE.txt">[FOR-857] append license files to the top-level LICENSE.txt</a>
+</li>
+<li>
+<a href="#%5BFOR-1080%5D+Add+Dispatcher+Notes+to+compatible+plugins">[FOR-1080] Add Dispatcher Notes to compatible plugins</a>
</li>
</ul>
</div>
@@ -305,23 +302,7 @@ document.write("Last Published: " + docu
</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"><strike>FOR-865</strike></a> &quot;Add missing entries to status.xml to generate the changes list&quot;.</p>
</div>
-<a name="N10029"></a><a name="%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release"></a>
-<h2 class="underlined_10">[FOR-855] verify the license situation prior to each release</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-855">http://issues.apache.org/jira/browse/FOR-855</a>
-</p>
-<p>This should be continually happening anyway, but immediately prior to each release we need to verify that our license situation is in order. This issue should not ever be closed, rather just move the &quot;Fix for Version&quot; on to the next release.<br/>
-<br/>
-Here are some of the tasks:<br/>
-<br/>
-A) Ensure that all supporting libraries have a corresponding license. Basically every jar file or other external package needs to have a *.license.txt file. Ensure that any license conditions are met, e.g. for some we must add an entry to NOTICE.txt, while for some others we must not. Remember to abide by the ASF guidelines (e.g. nothing more restrictive than the Apache License).<br/>
-<br/>
-B) Scan the whole trunk repository to add missing ASF license headers to source files and to ensure that the ASF license headers have not been accidently added to external files. See etc/relicense.txt<br/>
-<br/>
-C) Remove any author tags.</p>
-</div>
-<a name="N10035"></a><a name="%5BFOR-1108%5D+Dispatcher%2C+Cocoon+2.1+and+Windows"></a>
+<a name="N10029"></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>
@@ -329,23 +310,23 @@ C) Remove any author tags.</p>
</p>
<p>Since the update to Cocoon 2.1 Forrest and Dispatcher have broken on windows.</p>
</div>
-<a name="N10041"></a><a name="%5BFOR-1199%5D+the+plugins+%22deploy%22+and+%22release%22+target+need+to+depend+on+%22publish%22+property"></a>
-<h2 class="underlined_10">[FOR-1199] the plugins "deploy" and "release" target need to depend on "publish" property</h2>
+<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>
-<a href="http://issues.apache.org/jira/browse/FOR-1199">http://issues.apache.org/jira/browse/FOR-1199</a>
+<a href="http://issues.apache.org/jira/browse/FOR-855">http://issues.apache.org/jira/browse/FOR-855</a>
</p>
-<p>The &quot;publish&quot; property has been set in every plugin's build.xml file. Also reflected in the plugins descriptors, i.e. plugins/plugins.xml and whiteboard/plugins/whiteboard-plugins.xml
+<p>This should be continually happening anyway, but immediately prior to each release we need to verify that our license situation is in order. This issue should not ever be closed, rather just move the &quot;Fix for Version&quot; on to the next release.<br/>
<br/>
-
+Here are some of the tasks:<br/>
<br/>
-The generated &quot;Plugins Index&quot; utilise that property.
+A) Ensure that all supporting libraries have a corresponding license. Basically every jar file or other external package needs to have a *.license.txt file. Ensure that any license conditions are met, e.g. for some we must add an entry to NOTICE.txt, while for some others we must not. Remember to abide by the ASF guidelines (e.g. nothing more restrictive than the Apache License).<br/>
<br/>
-
+B) Scan the whole trunk repository to add missing ASF license headers to source files and to ensure that the ASF license headers have not been accidently added to external files. See etc/relicense.txt<br/>
<br/>
-The &quot;deploy&quot; and &quot;release&quot; targets need to fail gracefully if publish=false</p>
+C) Remove any author tags.</p>
</div>
-<a name="N1004D"></a><a name="%5BFOR-922%5D+update+all+docs+that+explain+sitemap+fragments"></a>
+<a name="N10041"></a><a name="%5BFOR-922%5D+update+all+docs+that+explain+sitemap+fragments"></a>
<h2 class="underlined_10">[FOR-922] update all docs that explain sitemap fragments</h2>
<div class="section">
<p>
@@ -361,21 +342,7 @@ The sitemaps were recently updated to us
<br/>
These changes need to be reflected in the current docs.</p>
</div>
-<a name="N10059"></a><a name="%5BFOR-857%5D+append+license+files+to+the+top-level+LICENSE.txt"></a>
-<h2 class="underlined_10">[FOR-857] append license files to the top-level LICENSE.txt</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-857">http://issues.apache.org/jira/browse/FOR-857</a>
-</p>
-<p>The license files for accompanying external products needs to be appended after the Apache License in the top-level $FORREST_HOME/LICENSE.txt file.
-<br/>
-
-<br/>
-Perhaps the current discussion on the legal-discuss mailing list will clarify
-<br/>
-<a href="http://www.apache.org/foundation/mailinglists.html#foundation-legal">http://www.apache.org/foundation/mailinglists.html#foundation-legal</a></p>
-</div>
-<a name="N10065"></a><a name="%5BFOR-1066%5D+Dispatcher+started+failing+on+seed+sample+site+recently+with+out-of-memory+error"></a>
+<a name="N1004D"></a><a name="%5BFOR-1066%5D+Dispatcher+started+failing+on+seed+sample+site+recently+with+out-of-memory+error"></a>
<h2 class="underlined_10">[FOR-1066] Dispatcher started failing on seed sample site recently with out-of-memory error</h2>
<div class="section">
<p>
@@ -391,17 +358,7 @@ See email:<br/>
<a href="http://mail-archives.apache.org/mod_mbox/forrest-dev/200801.mbox/%3c20080131070310.GE2051@igg.indexgeo.com.au%3e">http://mail-archives.apache.org/mod_mbox/forrest-dev/200801.mbox/%3c20080131070310.GE2051@igg.indexgeo.com.au%3e</a><br/>
Re: dispatcher hanging with out of memory errors</p>
</div>
-<a name="N10071"></a><a name="%5BFOR-1077%5D+new+CreationDate+causes+constant+differences+in+output+pdf+documents"></a>
-<h2 class="underlined_10">[FOR-1077] new CreationDate causes constant differences in output pdf documents</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-1077">http://issues.apache.org/jira/browse/FOR-1077</a>
-</p>
-<p>A problem has recently occurred with generating PDFs and publishing them. See the massive amount of commits to the Forrest &quot;site&quot; svn today when two different committers updated the website. Every PDF changed. I did some investigation and can see that a CreationDate is being added. This is of course is changing on every run of forrest.<br/>
-<br/>
-</p>
-</div>
-<a name="N1007D"></a><a name="%5BFOR-1184%5D+using+unreleased+code+for+some+supporting+products"></a>
+<a name="N10059"></a><a name="%5BFOR-1184%5D+using+unreleased+code+for+some+supporting+products"></a>
<h2 class="underlined_10">[FOR-1184] using unreleased code for some supporting products</h2>
<div class="section">
<p>
@@ -409,7 +366,7 @@ Re: dispatcher hanging with out of memor
</p>
<p>After the last release, an issue was brought to our attention about using unreleased code from other projects.</p>
</div>
-<a name="N10089"></a><a name="%5BFOR-889%5D+Use+by+Ant+of+newer+catalog+entity+resolver+failing+for+Windows"></a>
+<a name="N10065"></a><a name="%5BFOR-889%5D+Use+by+Ant+of+newer+catalog+entity+resolver+failing+for+Windows"></a>
<h2 class="underlined_10">[FOR-889] Use by Ant of newer catalog entity resolver failing for Windows</h2>
<div class="section">
<p>
@@ -421,7 +378,7 @@ See discussion in:<br/>
&nbsp;[heads up] Ant upgraded, please test<br/>
&nbsp;<a href="http://marc.theaimsgroup.com/?t=114800390100001">http://marc.theaimsgroup.com/?t=114800390100001</a></p>
</div>
-<a name="N10095"></a><a name="%5BFOR-1104%5D+pdf+output+warnings+%22paragraph+overflows+the+available+area%22"></a>
+<a name="N10071"></a><a name="%5BFOR-1104%5D+pdf+output+warnings+%22paragraph+overflows+the+available+area%22"></a>
<h2 class="underlined_10">[FOR-1104] pdf output warnings "paragraph overflows the available area"</h2>
<div class="section">
<p>
@@ -436,7 +393,7 @@ pluginDocs/plugins_0_90/usingPlugins.xml
<br/>
Perhaps there some way that we can word-wrap or break the long text lines.</p>
</div>
-<a name="N100A1"></a><a name="%5BFOR-1152%5D+regularly+ensure+cross-browser+consistency"></a>
+<a name="N1007D"></a><a name="%5BFOR-1152%5D+regularly+ensure+cross-browser+consistency"></a>
<h2 class="underlined_10">[FOR-1152] regularly ensure cross-browser consistency</h2>
<div class="section">
<p>
@@ -444,7 +401,7 @@ Perhaps there some way that we can word-
</p>
<p>Review the sites using cross-browser testing tools.</p>
</div>
-<a name="N100AD"></a><a name="%5BFOR-1149%5D+regularly+review+our+example+sites"></a>
+<a name="N10089"></a><a name="%5BFOR-1149%5D+regularly+review+our+example+sites"></a>
<h2 class="underlined_10">[FOR-1149] regularly review our example sites</h2>
<div class="section">
<p>
@@ -454,7 +411,7 @@ Perhaps there some way that we can word-
<br/>
Please leave this issue and subtasks as an open reminder of what needs to be done. Create separate issues for each problem that arises.</p>
</div>
-<a name="N100B9"></a><a name="%5BFOR-1150%5D+regularly+ensure+valid+HTML"></a>
+<a name="N10095"></a><a name="%5BFOR-1150%5D+regularly+ensure+valid+HTML"></a>
<h2 class="underlined_10">[FOR-1150] regularly ensure valid HTML</h2>
<div class="section">
<p>
@@ -462,7 +419,7 @@ Please leave this issue and subtasks as
</p>
<p>Ensure that HTML validates okay for the test document referred to in the parent issue. Use <a href="http://validator.w3.org/">http://validator.w3.org/</a></p>
</div>
-<a name="N100C5"></a><a name="%5BFOR-1151%5D+regularly+ensure+valid+CSS"></a>
+<a name="N100A1"></a><a name="%5BFOR-1151%5D+regularly+ensure+valid+CSS"></a>
<h2 class="underlined_10">[FOR-1151] regularly ensure valid CSS</h2>
<div class="section">
<p>
@@ -470,7 +427,7 @@ Please leave this issue and subtasks as
</p>
<p>Ensure that CSS validates okay for the test document referred to in the parent issue. Use <a href="http://jigsaw.w3.org/css-validator/">http://jigsaw.w3.org/css-validator/</a></p>
</div>
-<a name="N100D1"></a><a name="%5BFOR-1165%5D+Samples+Tab+does+not+stay+highlighted+when+sub-tab+or+sub-tab+menu+items+are+chosen+-+Pelt+Theme"></a>
+<a name="N100AD"></a><a name="%5BFOR-1165%5D+Samples+Tab+does+not+stay+highlighted+when+sub-tab+or+sub-tab+menu+items+are+chosen+-+Pelt+Theme"></a>
<h2 class="underlined_10">[FOR-1165] Samples Tab does not stay highlighted when sub-tab or sub-tab menu items are chosen - Pelt Theme</h2>
<div class="section">
<p>
@@ -480,7 +437,7 @@ Please leave this issue and subtasks as
<br/>
Then choose either 'Samples1' or 'Samples2' sub-tab and the 'Samples' highlight is removed. Correct behaviour as per Pelt Skin is for the highlighting color to remain.</p>
</div>
-<a name="N100DD"></a><a name="%5BFOR-644%5D+code-style+cleanup+for+xml+files"></a>
+<a name="N100B9"></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>
@@ -489,7 +446,7 @@ Then choose either 'Samples1' or 'Sample
<p>We have much inconsistent whitespace in all of our files. This is known to cause trouble in a collaborative environment. See discussion at: <a href="http://marc.theaimsgroup.com/?t=112450901100001">http://marc.theaimsgroup.com/?t=112450901100001</a> and <a href="http://marc.theaimsgroup.com/?t=112495618800002">http://marc.theaimsgroup.com/?t=112495618800002</a> and various linked discussions.<br/>
</p>
</div>
-<a name="N100E9"></a><a name="%5BFOR-1073%5D+link+elements+with+no+href+are+created+by+html-to-document.xsl+for+a%2Fname"></a>
+<a name="N100C5"></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>
@@ -500,7 +457,7 @@ Then choose either 'Samples1' or 'Sample
<br/>
There was also a mention of it previously on the dev list surrounding the recent FOP update branch work.</p>
</div>
-<a name="N100F5"></a><a name="%5BFOR-1187%5D+upgraded+PDF+plugin+was+not+deployed+properly"></a>
+<a name="N100D1"></a><a name="%5BFOR-1187%5D+upgraded+PDF+plugin+was+not+deployed+properly"></a>
<h2 class="underlined_10">[FOR-1187] upgraded PDF plugin was not deployed properly</h2>
<div class="section">
<p>
@@ -508,7 +465,15 @@ There was also a mention of it previousl
</p>
<p>Around January 2008 the PDF plugin was upgraded, gaining functionality that was only relevant to forrest-0.9-dev. It was re-deployed without changing the version numbers in the plugin descriptor.</p>
</div>
-<a name="N10101"></a><a name="%5BFOR-1166%5D+Search+Button+is+misplaced+to+the+right+in+some+browsers+-+Pelt+Theme"></a>
+<a name="N100DD"></a><a name="%5BFOR-1069%5D+add+notices+for+US+cryptographic+export+laws"></a>
+<h2 class="underlined_10">[FOR-1069] add notices for US cryptographic export laws</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-1069">http://issues.apache.org/jira/browse/FOR-1069</a>
+</p>
+<p>We need to investigate our SVN and add crypto notices as explained at <a href="http://www.apache.org/licenses/exports/">http://www.apache.org/licenses/exports/</a> and the legal-discuss mail list.</p>
+</div>
+<a name="N100E9"></a><a name="%5BFOR-1166%5D+Search+Button+is+misplaced+to+the+right+in+some+browsers+-+Pelt+Theme"></a>
<h2 class="underlined_10">[FOR-1166] Search Button is misplaced to the right in some browsers - Pelt Theme</h2>
<div class="section">
<p>
@@ -520,15 +485,7 @@ There was also a mention of it previousl
<br/>
Interestingly, it looks fine in Firefox on Windows. Also looks good in IE7 and Google Chrome on Windows.</p>
</div>
-<a name="N1010D"></a><a name="%5BFOR-1069%5D+add+notices+for+US+cryptographic+export+laws"></a>
-<h2 class="underlined_10">[FOR-1069] add notices for US cryptographic export laws</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-1069">http://issues.apache.org/jira/browse/FOR-1069</a>
-</p>
-<p>We need to investigate our SVN and add crypto notices as explained at <a href="http://www.apache.org/licenses/exports/">http://www.apache.org/licenses/exports/</a> and the legal-discuss mail list.</p>
-</div>
-<a name="N10119"></a><a name="%5BFOR-1168%5D+Sample+pages+that+fail+validation"></a>
+<a name="N100F5"></a><a name="%5BFOR-1168%5D+Sample+pages+that+fail+validation"></a>
<h2 class="underlined_10">[FOR-1168] Sample pages that fail validation</h2>
<div class="section">
<p>
@@ -570,7 +527,7 @@ pluginDocs/plugins_0_90/index.html
<br/>
</p>
</div>
-<a name="N10125"></a><a name="%5BFOR-1122%5D+Example+site+contentIntegration+currently+only+works+in+forrest+run+mode"></a>
+<a name="N10101"></a><a name="%5BFOR-1122%5D+Example+site+contentIntegration+currently+only+works+in+forrest+run+mode"></a>
<h2 class="underlined_10">[FOR-1122] Example site contentIntegration currently only works in forrest run mode</h2>
<div class="section">
<p>
@@ -578,21 +535,37 @@ pluginDocs/plugins_0_90/index.html
</p>
<p>Due to some remote content being aggregated into the site, 'forrest site' will fail as it can not resolve the remote locations.</p>
</div>
-<a name="N10131"></a><a name="%5BFOR-1200%5D+stop+re-generating+PDF+documents+on+Forrest+website"></a>
-<h2 class="underlined_10">[FOR-1200] stop re-generating PDF documents on Forrest website</h2>
+<a name="N1010D"></a><a name="%5BFOR-1077%5D+new+CreationDate+causes+constant+differences+in+output+pdf+documents"></a>
+<h2 class="underlined_10">[FOR-1077] new CreationDate causes constant differences in output pdf documents</h2>
<div class="section">
<p>
-<a href="http://issues.apache.org/jira/browse/FOR-1200">http://issues.apache.org/jira/browse/FOR-1200</a>
+<a href="http://issues.apache.org/jira/browse/FOR-1077">http://issues.apache.org/jira/browse/FOR-1077</a>
</p>
-<p>Due to various issues. See email:
-<br/>
-<a href="http://thread.gmane.org/gmane.text.xml.forrest.devel/27968">http://thread.gmane.org/gmane.text.xml.forrest.devel/27968</a>
+<p>A problem has recently occurred with generating PDFs and publishing them. See the massive amount of commits to the Forrest &quot;site&quot; svn today when two different committers updated the website. Every PDF changed. I did some investigation and can see that a CreationDate is being added. This is of course is changing on every run of forrest.<br/>
<br/>
-Subject: stop re-generating PDF documents on Forrest website
+</p>
+</div>
+<a name="N10119"></a><a name="%5BFOR-857%5D+append+license+files+to+the+top-level+LICENSE.txt"></a>
+<h2 class="underlined_10">[FOR-857] append license files to the top-level LICENSE.txt</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-857">http://issues.apache.org/jira/browse/FOR-857</a>
+</p>
+<p>The license files for accompanying external products needs to be appended after the Apache License in the top-level $FORREST_HOME/LICENSE.txt file.
<br/>
<br/>
-See <a href="http://issues.apache.org/jira/browse/FOR-1077" title="new CreationDate causes constant differences in output pdf documents">FOR-1077</a></p>
+Perhaps the current discussion on the legal-discuss mailing list will clarify
+<br/>
+<a href="http://www.apache.org/foundation/mailinglists.html#foundation-legal">http://www.apache.org/foundation/mailinglists.html#foundation-legal</a></p>
+</div>
+<a name="N10125"></a><a name="%5BFOR-1080%5D+Add+Dispatcher+Notes+to+compatible+plugins"></a>
+<h2 class="underlined_10">[FOR-1080] Add Dispatcher Notes to compatible plugins</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-1080">http://issues.apache.org/jira/browse/FOR-1080</a>
+</p>
+<p>Some (most?) Plugins are Dispatcher compatible, notes should be added to each plugin documentation summarising how to use the plugin in dispatcher enabled projects - such as adding contracts that make use of a plugin.</p>
</div>
</div>
<!--+
Modified: forrest/site/gump.html
URL: http://svn.apache.org/viewvc/forrest/site/gump.html?rev=960152&r1=960151&r2=960152&view=diff
==============================================================================
--- forrest/site/gump.html (original)
+++ forrest/site/gump.html Sat Jul 3 03:55:02 2010
@@ -236,17 +236,31 @@ document.write("Last Published: " + docu
<div id="front-matter"></div>
<p>
- Apache Gump builds Apache Forrest trunk each day. If dependencies (e.g.
- Cocoon and certain blocks) fail, then of course the build of Forrest will
- fail.
+
+<a href="http://gump.apache.org/">Apache Gump</a> builds Apache Forrest
+ trunk and the latest development versions of each of our dependencies.
+ This enables early detection of issues. Part of Gump's aim is to
+ draw people beyond the project boundaries and assist with community
+ integration and collaboration.
+ </p>
+
+<p>
+ Because Forrest has many dependencies, we happen towards the end of
+ the run.
+ If dependencies (e.g. Apache Cocoon and certain blocks, Apache Xalan, etc.)
+ fail, then of course the build of Forrest will fail.
+ </p>
+
+<p>
+ The successful use of Forrest via Gump, indicates that we could update
+ our supporting products to more recent versions.
</p>
<div class="note">
<div class="label">Note</div>
<div class="content">
- The main build of Forrest by Gump is disabled. If Gump would build
- Cocoon-2.1 branch or use built artefacts, then we could re-instate the
- build. Some other parts of Forrest are still built, see below.
+ Gump is using a packaged version of Cocoon-2.1 (Cocoon-2.1.11) at the
+ moment.
</div>
</div>
@@ -281,16 +295,33 @@ document.write("Last Published: " + docu
<ul>
<li>
-<a href="http://vmgump.apache.org/gump/public/forrest/forrest/">forrest</a> (disabled)</li>
+<a href="http://vmgump.apache.org/gump/public/forrest/forrest/">forrest</a> (active)<br>
+ This is the core of forrest.
+ </li>
<li>
-<a href="http://vmgump.apache.org/gump/public/forrest/forrest-test/">forrest-test</a> (disabled)</li>
+<a href="http://vmgump.apache.org/gump/public/forrest/forrest-test/">forrest-test</a> (needs attention)<br>
+ This does 'forrest test' to build our "seed-sample" site.
+ <div class="fixme">
+<div class="label">Fixme (crossley)</div>
+<div class="content">
+ See <a href="https://issues.apache.org/jira/browse/FOR-1201">FOR-1201</a>
+ which is currently adjusting our Gump descriptor to obtain a run of "forrest-test".
+ </div>
+</div>
+
+</li>
<li>
-<a href="http://vmgump.apache.org/gump/public/forrest/forrest-forrestbar/">forrest-forrestbar</a> (active)</li>
+<a href="http://vmgump.apache.org/gump/public/forrest/forrest-forrestbar/">forrest-forrestbar</a> (active)<br>
+ The ForrestBar tool.
+ </li>
<li>
-<a href="http://vmgump.apache.org/gump/public/forrest/forrest-rat/">forrest-rat</a> (active)</li>
+<a href="http://vmgump.apache.org/gump/public/forrest/forrest-rat/">forrest-rat</a> (active)<br>
+ Using Apache RAT (Release Audit Tool) to give some indication of the
+ the state of our source code headers and some other license aspects.
+ </li>
</ul>