forrest-site-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r529980 - in /forrest/site: .htaccess forrest-issues.html forrest-issues.pdf
Date Wed, 18 Apr 2007 11:17:11 GMT
Author: crossley
Date: Wed Apr 18 04:17:10 2007
New Revision: 529980

URL: http://svn.apache.org/viewvc?view=rev&rev=529980
Log:
Automatic publish from forrestbot

Modified:
    forrest/site/.htaccess
    forrest/site/forrest-issues.html
    forrest/site/forrest-issues.pdf

Modified: forrest/site/.htaccess
URL: http://svn.apache.org/viewvc/forrest/site/.htaccess?view=diff&rev=529980&r1=529979&r2=529980
==============================================================================
--- forrest/site/.htaccess (original)
+++ forrest/site/.htaccess Wed Apr 18 04:17:10 2007
@@ -5,6 +5,8 @@
 # FIXME: Do we still need this? See FOR-877
 AddDefaultCharset UTF-8
 
+AddType application/x-xpinstall .xpi
+
 # Some old documents need special handling
 RedirectMatch ^/mail-archives(.*) http://forrest.apache.org/mail-lists$1
 RedirectMatch .*proposal-asf-publish.html http://people.apache.org/~crossley/proposal-asf-publish.html

Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewvc/forrest/site/forrest-issues.html?view=diff&rev=529980&r1=529979&r2=529980
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Wed Apr 18 04:17:10 2007
@@ -213,6 +213,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-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-572%5D+run+a+memory+profiler+while+forrest+is+operating">[FOR-572]
run a memory profiler while forrest is operating</a>
 </li>
 <li>
@@ -266,9 +269,6 @@
 <li>
 <a href="#%5BFOR-770%5D+Locationmaplogs+should+show+which+sitemap+the+request+is+coming+from">[FOR-770]
Locationmaplogs should show which sitemap the request is coming from</a>
 </li>
-<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>
 </ul>
 </div>
 <div class="note">
@@ -405,7 +405,15 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N10059"></a><a name="%5BFOR-572%5D+run+a+memory+profiler+while+forrest+is+operating"></a>
+<a name="N10059"></a><a name="%5BFOR-868%5D+add+relevant+notes+to+the+%22Upgrading%22+xdoc"></a>
+<h2 class="underlined_10">[FOR-868] add relevant notes to the "Upgrading" xdoc</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-868">http://issues.apache.org/jira/browse/FOR-868</a>
+</p>
+<p>We need to add some notes to the upgrading_0*.html doc for the upcoming release.
This would most easily be done after attending to &lt;a href="https://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="N10065"></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>
@@ -413,7 +421,7 @@
 </p>
 <p>We need to run a memory profiler while forrest is operating.</p>
 </div>
-<a name="N10065"></a><a name="%5BFOR-588%5D+Design+new+configuration+system"></a>
+<a name="N10071"></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>
@@ -421,7 +429,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="N10071"></a><a name="%5BFOR-707%5D+Document+i18n+features+of+Forrest"></a>
+<a name="N1007D"></a><a name="%5BFOR-707%5D+Document+i18n+features+of+Forrest"></a>
 <h2 class="underlined_10">[FOR-707] Document i18n features of Forrest</h2>
 <div class="section">
 <p>
@@ -435,7 +443,7 @@
 &lt;br/&gt;
 We could, at the very least use the locationmap to pull this content into our site [OT: I
wonder if this could be a way to generate more documentation?)</p>
 </div>
-<a name="N1007D"></a><a name="%5BFOR-957%5D+how+to+remove+dependencies"></a>
+<a name="N10089"></a><a name="%5BFOR-957%5D+how+to+remove+dependencies"></a>
 <h2 class="underlined_10">[FOR-957] how to remove dependencies</h2>
 <div class="section">
 <p>
@@ -443,7 +451,7 @@
 </p>
 <p>fsfdsfdsfds</p>
 </div>
-<a name="N10089"></a><a name="%5BFOR-986%5D+Dispatcher+war+fails+to+build"></a>
+<a name="N10095"></a><a name="%5BFOR-986%5D+Dispatcher+war+fails+to+build"></a>
 <h2 class="underlined_10">[FOR-986] Dispatcher war fails to build</h2>
 <div class="section">
 <p>
@@ -463,7 +471,7 @@
 &lt;br/&gt;
 To work around this issue just put a skinconf.xml in place</p>
 </div>
-<a name="N10095"></a><a name="%5BFOR-388%5D+Use+plugins+in-place+if+src+available"></a>
+<a name="N100A1"></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>
@@ -475,7 +483,7 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N100A1"></a><a name="%5BFOR-250%5D+only+add+the+compliance+logos+if+the+html+is+valid"></a>
+<a name="N100AD"></a><a name="%5BFOR-250%5D+only+add+the+compliance+logos+if+the+html+is+valid"></a>
 <h2 class="underlined_10">[FOR-250] only add the compliance logos if the html is valid</h2>
 <div class="section">
 <p>
@@ -483,7 +491,7 @@
 </p>
 <p>Currently the compliance logos are only applied to any page called &amp;quot;index.html&amp;quot;.
It would be nice if we could automatically determine if the final output was valid and apply
the compliance logos accordingly.</p>
 </div>
-<a name="N100AD"></a><a name="%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links"></a>
+<a name="N100B9"></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>
@@ -493,7 +501,7 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N100B9"></a><a name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
+<a name="N100C5"></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>
@@ -501,7 +509,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="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>
@@ -510,7 +518,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>
@@ -518,7 +526,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>
@@ -528,7 +536,7 @@
 &lt;br/&gt;
 This is most likely a side-effect of the workaround for issue &lt;a href="https://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>
@@ -536,7 +544,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>
@@ -544,7 +552,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>
@@ -558,7 +566,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>
@@ -566,7 +574,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>
@@ -584,7 +592,7 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N10125"></a><a name="%5BFOR-770%5D+Locationmaplogs+should+show+which+sitemap+the+request+is+coming+from"></a>
+<a name="N10131"></a><a name="%5BFOR-770%5D+Locationmaplogs+should+show+which+sitemap+the+request+is+coming+from"></a>
 <h2 class="underlined_10">[FOR-770] Locationmaplogs should show which sitemap the request
is coming from</h2>
 <div class="section">
 <p>
@@ -599,25 +607,6 @@
 &amp;quot;Examining Locationmap for &amp;quot;project.foo&amp;quot; on behald
of /raw.xmap (line XYZ)&amp;quot;&lt;br/&gt;
 &lt;br/&gt;
 </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>
-<h2 class="underlined_10">[FOR-776] rationalise the pluginTemplate and current plugins
to have minimal configuration files, etc.</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-776">http://issues.apache.org/jira/browse/FOR-776</a>
-</p>
-<p>forrest.properties can have minimal entries and rely on the default.forrest.properties&lt;br/&gt;
-Remove PDF from each &amp;quot;project.required.plugins&amp;quot;&lt;br/&gt;
-&lt;br/&gt;
-skinconf.xml needs to be ready-to-go for Apache Forrest hosted plugins. Helps with keeping
the plugin docs consistent. (The need for skinconf.xml will probably go away with the new
Dispatcher.)&lt;br/&gt;
-&lt;br/&gt;
-Fix whitespace in pluginTemplate files and existing plugins. Helps to use diff to keep consistent
config.&lt;br/&gt;
-&lt;br/&gt;
-xdocs/images should be in documentation/resources/images&lt;br/&gt;
-&lt;br/&gt;
-site.xml needs to be consistent and remove any unneccessary files for xdocs.&lt;br/&gt;
-&lt;br/&gt;
-Tidy up the pluginTempate/status.xml</p>
 </div>
 </div>
 <!--+

Modified: forrest/site/forrest-issues.pdf
URL: http://svn.apache.org/viewvc/forrest/site/forrest-issues.pdf?view=diff&rev=529980&r1=529979&r2=529980
==============================================================================
Binary files - no diff available.



Mime
View raw message