forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r453465 - in /forrest/site: events.html events.pdf forrest-issues.html forrest-issues.pdf procedures/release/How_to_release.html procedures/release/How_to_release.pdf
Date Fri, 06 Oct 2006 02:10:49 GMT
Author: crossley
Date: Thu Oct  5 19:10:48 2006
New Revision: 453465

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

Modified:
    forrest/site/events.html
    forrest/site/events.pdf
    forrest/site/forrest-issues.html
    forrest/site/forrest-issues.pdf
    forrest/site/procedures/release/How_to_release.html
    forrest/site/procedures/release/How_to_release.pdf

Modified: forrest/site/events.html
URL: http://svn.apache.org/viewvc/forrest/site/events.html?view=diff&rev=453465&r1=453464&r2=453465
==============================================================================
--- forrest/site/events.html (original)
+++ forrest/site/events.html Thu Oct  5 19:10:48 2006
@@ -241,6 +241,11 @@
 </li>
 <li>
 <a href="#apachecon-us-2006">ApacheCon US 2006 (9-13 October 2006)</a>
+<ul class="minitoc">
+<li>
+<a href="#WE21-austin-2006">ApacheCon Session: WE21: Single Source Publishing with
Apache Forrest</a>
+</li>
+</ul>
 </li>
 </ul>
 </li>
@@ -307,13 +312,24 @@
          - Please make plans to join us for the conference in
          Austin, Texas, USA on 9-13 October 2006.
         </p>
+<p>
+          Apart from all of the general ApacheCon events, there are a number of
+          Forrest-specific events. In chronological order ...
+        </p>
+<a name="N10031"></a><a name="WE21-austin-2006"></a>
+<h4>ApacheCon Session: WE21: Single Source Publishing with Apache Forrest</h4>
+<p>
+            Wednesday 11 October - Official ApacheCon session
+            conducted by Ferdinand Soethe.
+            <a href="http://www.us.apachecon.com/html/sessions.html">Read more</a>.
+          </p>
 </div>
 
     
-<a name="N10030"></a><a name="past"></a>
+<a name="N10041"></a><a name="past"></a>
 <h2 class="underlined_10">Past events</h2>
 <div class="section">
-<a name="N10036"></a><a name="apachecon-eu-2006"></a>
+<a name="N10047"></a><a name="apachecon-eu-2006"></a>
 <h3 class="underlined_5">ApacheCon EU 2006 (26-30 June)</h3>
 <p>
          
@@ -325,7 +341,7 @@
           Apart from all of the general ApacheCon events, there are a number of
           Forrest-specific events. In chronological order ...
         </p>
-<a name="N10046"></a><a name="FR19-dublin-2006"></a>
+<a name="N10057"></a><a name="FR19-dublin-2006"></a>
 <h4>ApacheCon Session: FR19: Single Source Publishing with Apache Forrest</h4>
 <p>
             Friday 30 June - Official ApacheCon session
@@ -337,7 +353,7 @@
 <div class="label">Note</div>
 <div class="content">This session is has been re-scheduled for Friday 30 June 14:30-15:30.</div>
 </div>
-<a name="N10058"></a><a name="apachecon-us-2005"></a>
+<a name="N10069"></a><a name="apachecon-us-2005"></a>
 <h3 class="underlined_5">ApacheCon US 2005 (10-14 December)</h3>
 <p>
           
@@ -348,7 +364,7 @@
           Apart from all of the general ApacheCon events, there is one
           Forrest-specific event.
         </p>
-<a name="N10068"></a><a name="fs-ac-us-2005"></a>
+<a name="N10079"></a><a name="fs-ac-us-2005"></a>
 <h4>ApacheCon Session: Single Source Publishing with Apache Forrest</h4>
 <p>
             Tuesday 13 December at 09:00 to 10:00 - Official ApacheCon session
@@ -357,7 +373,7 @@
             Schedule</a> Session TU01.
             The event is only open to ApacheCon attendees.
           </p>
-<a name="N10077"></a><a name="apachecon-eu-2005"></a>
+<a name="N10088"></a><a name="apachecon-eu-2005"></a>
 <h3 class="underlined_5">ApacheCon Europe 2005 (18-22 July)</h3>
 <p>
         
@@ -369,7 +385,7 @@
         Apart from all of the general ApacheCon events, there are a number of
         Forrest-specific events. In chronological order ...
       </p>
-<a name="N10087"></a><a name="ht-stuttgart-2005"></a>
+<a name="N10098"></a><a name="ht-stuttgart-2005"></a>
 <h4>Apache committers hackathon</h4>
 <p>
           Monday 18 July and Tuesday 19 July all day - Open to any Apache
@@ -377,7 +393,7 @@
           about Apache Forrest and maybe fix some bugs. We will probably
           collaborate with the Apache Lenya committers too.
         </p>
-<a name="N10091"></a><a name="ws-stuttgart-2005"></a>
+<a name="N100A2"></a><a name="ws-stuttgart-2005"></a>
 <h4>Apache Forrest workshop on Views</h4>
 <p>
           Monday 18 July commencing at 18:30 - We will go out to dinner and then
@@ -390,7 +406,7 @@
           The event is open to anybody, you don't need to be attending ApacheCon.
           Venue and Directions: Gather at the foyer of the ApacheCon.
         </p>
-<a name="N1009B"></a><a name="ua-stuttgart-2005"></a>
+<a name="N100AC"></a><a name="ua-stuttgart-2005"></a>
 <h4>Usability professionals meeting</h4>
 <p>
           Tuesday 19 July commencing at 18:30 - Johannes Schaefer will
@@ -399,7 +415,7 @@
           See
           <a href="http://www.gui-design.de/ak/ak_050719.htm">further information</a>.
         </p>
-<a name="N100A9"></a><a name="rf-stuttgart-2005"></a>
+<a name="N100BA"></a><a name="rf-stuttgart-2005"></a>
 <h4>ApacheCon Session: Single Source Publishing with Apache Forrest</h4>
 <p>
           Wednesday 20 July at 14:30 to 15:30 - Official ApacheCon session
@@ -408,7 +424,7 @@
           Schedule</a> Session WE16.
           The event is only open to ApacheCon attendees.
         </p>
-<a name="N100B7"></a><a name="gt-stuttgart-2005"></a>
+<a name="N100C8"></a><a name="gt-stuttgart-2005"></a>
 <h4>Apache Forrest get-together</h4>
 <p>
           Wednesday 20 July commencing at 20:00 - Informal get together to

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

Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewvc/forrest/site/forrest-issues.html?view=diff&rev=453465&r1=453464&r2=453465
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Thu Oct  5 19:10:48 2006
@@ -189,33 +189,36 @@
 <div id="minitoc-area">
 <ul class="minitoc">
 <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-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-865%5D+Add+missing+entries+to+status.xml+to+generate+the+changes+list">[FOR-865]
Add missing entries to status.xml to generate the changes list</a>
 </li>
 <li>
-<a href="#%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode">[FOR-735]
Plugins are not correctly deployed in webapp mode</a>
+<a href="#%5BFOR-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-711%5D+Cache+results+from+the+Locationmap">[FOR-711] Cache results
from the Locationmap</a>
+<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-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo">[FOR-742]
trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo</a>
+<a href="#%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode">[FOR-735]
Plugins are not correctly deployed in webapp mode</a>
 </li>
 <li>
-<a href="#%5BFOR-533%5D+Auto+Generate+plugins.xml+entry">[FOR-533] Auto Generate plugins.xml
entry</a>
+<a href="#%5BFOR-711%5D+Cache+results+from+the+Locationmap">[FOR-711] Cache results
from the Locationmap</a>
+</li>
+<li>
+<a href="#%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo">[FOR-742]
trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo</a>
 </li>
 <li>
 <a href="#%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes">[FOR-241]
character entities (e.g. ampersand) are expanded again for href or src attributes</a>
 </li>
 <li>
+<a href="#%5BFOR-200%5D+Locationmap+for+Forrest+and+Users">[FOR-200] Locationmap for
Forrest and Users</a>
+</li>
+<li>
 <a href="#%5BFOR-546%5D+Sitemap+reference+doc+should+be+updated+to+reflect+plugin+architecture">[FOR-546]
Sitemap reference doc should be updated to reflect plugin architecture</a>
 </li>
 <li>
@@ -234,9 +237,6 @@
 <a href="#%5BFOR-901%5D+Review+the+note+on+the+home+page+about+first+forrest+run+and+retrieving+plugins+from+network">[FOR-901]
Review the note on the home page about first forrest run and retrieving plugins from network</a>
 </li>
 <li>
-<a href="#%5BFOR-200%5D+Locationmap+for+Forrest+and+Users">[FOR-200] Locationmap for
Forrest and Users</a>
-</li>
-<li>
 <a href="#%5BFOR-906%5D+locationmap+documentation+explain+this-to-that.xsl+naming+convention+and+default+lm+matches">[FOR-906]
locationmap documentation explain this-to-that.xsl naming convention and default lm matches</a>
 </li>
 <li>
@@ -246,13 +246,16 @@
 <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-936%5D+Forrest+%22looses%22+the+locale+when+switching+pages">[FOR-936]
Forrest "looses" the locale when switching pages</a>
+</li>
+<li>
 <a href="#%5BFOR-537%5D+Plugin+documentation+sitemap+references">[FOR-537] Plugin documentation
sitemap references</a>
 </li>
 <li>
-<a href="#%5BFOR-671%5D+Layering+error+of+HTML+headings+breaks+rest+of+the+page+w%2Fo+warning">[FOR-671]
Layering error of HTML headings breaks rest of the page w/o warning</a>
+<a href="#%5BFOR-635%5D+images+not+reproduced+in+PDFs%2C+if+sources+are+in+xdocs%2Fimages+directory">[FOR-635]
images not reproduced in PDFs, if sources are in xdocs/images directory</a>
 </li>
 <li>
-<a href="#%5BFOR-861%5D+Update+locationmap+docs+for+working+with+remote+files">[FOR-861]
Update locationmap docs for working with remote files</a>
+<a href="#%5BFOR-671%5D+Layering+error+of+HTML+headings+breaks+rest+of+the+page+w%2Fo+warning">[FOR-671]
Layering error of HTML headings breaks rest of the page w/o warning</a>
 </li>
 <li>
 <a href="#%5BFOR-731%5D+empty+linkmap.html+document%2C+side-effect+of+workaround+to+FOR-675">[FOR-731]
empty linkmap.html document, side-effect of workaround to FOR-675</a>
@@ -260,9 +263,6 @@
 <li>
 <a href="#%5BFOR-767%5D+Forrestbot+webapp+reports+succesful+even+when+there+are+broken+links">[FOR-767]
Forrestbot webapp reports succesful even when there are broken links</a>
 </li>
-<li>
-<a href="#%5BFOR-635%5D+images+not+reproduced+in+PDFs%2C+if+sources+are+in+xdocs%2Fimages+directory">[FOR-635]
images not reproduced in PDFs, if sources are in xdocs/images directory</a>
-</li>
 </ul>
 </div>
 <div class="note">
@@ -273,15 +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-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="http://issues.apache.org/jira/browse/FOR-865"
title="Add missing entries to status.xml to generate the changes list"&gt;FOR-865&lt;/a&gt;
&amp;quot;Add missing entries to status.xml to generate the changes list&amp;quot;.</p>
-</div>
-<a name="N1001D"></a><a name="%5BFOR-855%5D+verify+the+license+situation+prior+to+each+release"></a>
+<a name="N10011"></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>
@@ -303,7 +295,7 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N10029"></a><a name="%5BFOR-865%5D+Add+missing+entries+to+status.xml+to+generate+the+changes+list"></a>
+<a name="N1001D"></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>
@@ -321,39 +313,31 @@
 &lt;br/&gt;
 &lt;a href="http://marc.theaimsgroup.com/?t=114274836600001"&gt;http://marc.theaimsgroup.com/?t=114274836600001&lt;/a&gt;</p>
 </div>
-<a name="N10035"></a><a name="%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode"></a>
-<h2 class="underlined_10">[FOR-735] Plugins are not correctly deployed in webapp mode</h2>
+<a name="N10029"></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-735">http://issues.apache.org/jira/browse/FOR-735</a>
+<a href="http://issues.apache.org/jira/browse/FOR-868">http://issues.apache.org/jira/browse/FOR-868</a>
 </p>
-<p>(At this point I didn't try this scenario step by step any more; basically it is
what we did to setup the site, except that we copied our project data from forrest 0.6 before
trying the pdf links)
-&lt;br/&gt;
-
-&lt;br/&gt;
-- run forrest webapp to create an empty webapp
-&lt;br/&gt;
-- configure Tomcat to run the webapp (we did it by creating a context descriptor and put
it onder Tomcat's config directory)
-&lt;br/&gt;
-- the pdf links give an error &amp;quot;Resource Not Found&amp;quot;</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;FOR-865&lt;/a&gt;
&amp;quot;Add missing entries to status.xml to generate the changes list&amp;quot;.</p>
 </div>
-<a name="N10041"></a><a name="%5BFOR-711%5D+Cache+results+from+the+Locationmap"></a>
-<h2 class="underlined_10">[FOR-711] Cache results from the Locationmap</h2>
+<a name="N10035"></a><a name="%5BFOR-533%5D+Auto+Generate+plugins.xml+entry"></a>
+<h2 class="underlined_10">[FOR-533] Auto Generate plugins.xml entry</h2>
 <div class="section">
 <p>
-<a href="http://issues.apache.org/jira/browse/FOR-711">http://issues.apache.org/jira/browse/FOR-711</a>
+<a href="http://issues.apache.org/jira/browse/FOR-533">http://issues.apache.org/jira/browse/FOR-533</a>
 </p>
-<p>Now that we are using the locationmap extensively it is showing up just how innefficient
it is. The problem is that for the majority of requests there are multiple reqeuests to the
locationmap. We can make things much faster (especially on the first page request) by caching
results in the locationmap.
+<p>The information in the plugins.xml file would be better kept in the plugin directory
and added to the plugins.xml file when deployed. This would reduce the amount of duplication
in the plugins config files.
 &lt;br/&gt;
 
 &lt;br/&gt;
-I think a simple cache will sufice, lets just provide a static hashmap using the hint as
a key and, of course, the location as the value.
+All the necessary values are now in the plugin build.xml file.
 &lt;br/&gt;
 
 &lt;br/&gt;
-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 &lt;a href="http://issues.apache.org/jira/browse/FOR-701" title="Missing
locationmap entry gives poor error"&gt;FOR-701&lt;/a&gt;)</p>
+This change will require that the plugins.xml file be retrieved from the build directory
rather than the plugins directory when building the plugin documentation pages. We will therefore
need a fall back to retrieve this file from the network if it is not currently available -
this can be done with the locationmap</p>
 </div>
-<a name="N1004D"></a><a name="%5BFOR-639%5D+define+terminology+for+the+various+aspects+of+Dispatcher"></a>
+<a name="N10041"></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>
@@ -365,35 +349,51 @@
 &lt;br/&gt;
 </p>
 </div>
-<a name="N10059"></a><a name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
-<h2 class="underlined_10">[FOR-742] trouble accessing unversioned plugin for a released
version of Forrest, e.g. projectInfo</h2>
+<a name="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>
-<a href="http://issues.apache.org/jira/browse/FOR-742">http://issues.apache.org/jira/browse/FOR-742</a>
+<a href="http://issues.apache.org/jira/browse/FOR-735">http://issues.apache.org/jira/browse/FOR-735</a>
 </p>
-<p>The plugin retrieval and deployment process are not quite correct. Recently the
projectInfo plugin had its version number incremented and the &amp;quot;unversioned&amp;quot;
plugin now relates specifically to 0.8-dev version. That prevents 0.7 from accessing the relevant
plugin.
+<p>(At this point I didn't try this scenario step by step any more; basically it is
what we did to setup the site, except that we copied our project data from forrest 0.6 before
trying the pdf links)
 &lt;br/&gt;
 
 &lt;br/&gt;
-The solution is discussed here:
+- run forrest webapp to create an empty webapp
 &lt;br/&gt;
-&lt;a href="http://marc.theaimsgroup.com/?t=113176328300002"&gt;http://marc.theaimsgroup.com/?t=113176328300002&lt;/a&gt;</p>
+- configure Tomcat to run the webapp (we did it by creating a context descriptor and put
it onder Tomcat's config directory)
+&lt;br/&gt;
+- the pdf links give an error &amp;quot;Resource Not Found&amp;quot;</p>
 </div>
-<a name="N10065"></a><a name="%5BFOR-533%5D+Auto+Generate+plugins.xml+entry"></a>
-<h2 class="underlined_10">[FOR-533] Auto Generate plugins.xml entry</h2>
+<a name="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>
-<a href="http://issues.apache.org/jira/browse/FOR-533">http://issues.apache.org/jira/browse/FOR-533</a>
+<a href="http://issues.apache.org/jira/browse/FOR-711">http://issues.apache.org/jira/browse/FOR-711</a>
 </p>
-<p>The information in the plugins.xml file would be better kept in the plugin directory
and added to the plugins.xml file when deployed. This would reduce the amount of duplication
in the plugins config files.
+<p>Now that we are using the locationmap extensively it is showing up just how innefficient
it is. The problem is that for the majority of requests there are multiple reqeuests to the
locationmap. We can make things much faster (especially on the first page request) by caching
results in the locationmap.
 &lt;br/&gt;
 
 &lt;br/&gt;
-All the necessary values are now in the plugin build.xml file.
+I think a simple cache will sufice, lets just provide a static hashmap using the hint as
a key and, of course, the location as the value.
 &lt;br/&gt;
 
 &lt;br/&gt;
-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>
+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 &lt;a href="http://issues.apache.org/jira/browse/FOR-701" title="Missing
locationmap entry gives poor error"&gt;FOR-701&lt;/a&gt;)</p>
+</div>
+<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>
+<a href="http://issues.apache.org/jira/browse/FOR-742">http://issues.apache.org/jira/browse/FOR-742</a>
+</p>
+<p>The plugin retrieval and deployment process are not quite correct. Recently the
projectInfo plugin had its version number incremented and the &amp;quot;unversioned&amp;quot;
plugin now relates specifically to 0.8-dev version. That prevents 0.7 from accessing the relevant
plugin.
+&lt;br/&gt;
+
+&lt;br/&gt;
+The solution is discussed here:
+&lt;br/&gt;
+&lt;a href="http://marc.theaimsgroup.com/?t=113176328300002"&gt;http://marc.theaimsgroup.com/?t=113176328300002&lt;/a&gt;</p>
 </div>
 <a name="N10071"></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>
@@ -441,7 +441,19 @@
 &lt;br/&gt;
 the ampersand in the link href attribute is not.</p>
 </div>
-<a name="N1007D"></a><a name="%5BFOR-546%5D+Sitemap+reference+doc+should+be+updated+to+reflect+plugin+architecture"></a>
+<a name="N1007D"></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>
+<a href="http://issues.apache.org/jira/browse/FOR-200">http://issues.apache.org/jira/browse/FOR-200</a>
+</p>
+<p>The locationmap gives us the ability to specify where sources are, both for Forrest
and for the users.
+&lt;br/&gt;
+
+&lt;br/&gt;
+Beware that it will not work for raw files that are not linked, as this &amp;quot;feature&amp;quot;
currently uses a fixed dir being being copied by Ant.</p>
+</div>
+<a name="N10089"></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>
@@ -473,7 +485,7 @@
 &lt;br/&gt;
 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="N10089"></a><a name="%5BFOR-666%5D+clarify+the+sitemap+matches+etc.+in+FAQ+about+non-skinned+html"></a>
+<a name="N10095"></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>
@@ -489,7 +501,7 @@
 &lt;br/&gt;
 &amp;lt;map:match pattern=&amp;quot;old_site/**.html&amp;quot;&amp;gt;</p>
 </div>
-<a name="N10095"></a><a name="%5BFOR-726%5D+use+locationmap+in+all+of+the+plugins"></a>
+<a name="N100A1"></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>
@@ -501,7 +513,7 @@
 &lt;br/&gt;
 (Perhaps we need Jira sub-tasks for each plugin.)</p>
 </div>
-<a name="N100A1"></a><a name="%5BFOR-765%5D+forrest+war+gets+NoSuchMethodError+for+some+core+transformer"></a>
+<a name="N100AD"></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>
@@ -509,7 +521,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="N100AD"></a><a name="%5BFOR-776%5D+rationalise+the+pluginTemplate+and+current+plugins+to+have+minimal+configuration+files%2C+etc."></a>
+<a name="N100B9"></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>
@@ -539,7 +551,7 @@
 &lt;br/&gt;
 Tidy up the pluginTempate/status.xml</p>
 </div>
-<a name="N100B9"></a><a name="%5BFOR-901%5D+Review+the+note+on+the+home+page+about+first+forrest+run+and+retrieving+plugins+from+network"></a>
+<a name="N100C5"></a><a name="%5BFOR-901%5D+Review+the+note+on+the+home+page+about+first+forrest+run+and+retrieving+plugins+from+network"></a>
 <h2 class="underlined_10">[FOR-901] Review the note on the home page about first forrest
run and retrieving plugins from network</h2>
 <div class="section">
 <p>
@@ -549,18 +561,6 @@
 &lt;br/&gt;
 &lt;a href="http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/index.xml?r1=365495&amp;r2=365494&amp;pathrev=365495"&gt;http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/index.xml?r1=365495&amp;amp;r2=365494&amp;amp;pathrev=365495&lt;/a&gt;</p>
 </div>
-<a name="N100C5"></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>
-<a href="http://issues.apache.org/jira/browse/FOR-200">http://issues.apache.org/jira/browse/FOR-200</a>
-</p>
-<p>The locationmap gives us the ability to specify where sources are, both for Forrest
and for the users.
-&lt;br/&gt;
-
-&lt;br/&gt;
-Beware that it will not work for raw files that are not linked, as this &amp;quot;feature&amp;quot;
currently uses a fixed dir being being copied by Ant.</p>
-</div>
 <a name="N100D1"></a><a name="%5BFOR-906%5D+locationmap+documentation+explain+this-to-that.xsl+naming+convention+and+default+lm+matches"></a>
 <h2 class="underlined_10">[FOR-906] locationmap documentation explain this-to-that.xsl
naming convention and default lm matches</h2>
 <div class="section">
@@ -601,7 +601,35 @@
 &lt;br/&gt;
 These changes need to be reflected in the current docs.</p>
 </div>
-<a name="N100F5"></a><a name="%5BFOR-537%5D+Plugin+documentation+sitemap+references"></a>
+<a name="N100F5"></a><a name="%5BFOR-936%5D+Forrest+%22looses%22+the+locale+when+switching+pages"></a>
+<h2 class="underlined_10">[FOR-936] Forrest "looses" the locale when switching pages</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-936">http://issues.apache.org/jira/browse/FOR-936</a>
+</p>
+<p>When moving from one page to another and switching locales in between, the chosen
locale is lost when entering the new page. To reproduce:
+&lt;br/&gt;
+
+&lt;br/&gt;
+1) set up and run forrest with i18n ON
+&lt;br/&gt;
+2) open a localized page
+&lt;br/&gt;
+3) switch locale by appending '?locale=XY' in the address field
+&lt;br/&gt;
+4) open another page available in both the original locale (before the switch) and the new
locale XY
+&lt;br/&gt;
+5) notice how the new page is displayed in the original locale, NOT the expected XY locale
+&lt;br/&gt;
+
+&lt;br/&gt;
+Although one could argue that the described behaviour is wanted in some cases, I believe
that to most users it would be natural that the locale is &amp;quot;sticky&amp;quot;
once changed - it should not change back by itself. Thus, the &amp;quot;sticky&amp;quot;
behaviour should be default in Forrest.
+&lt;br/&gt;
+
+&lt;br/&gt;
+The fix is simple, patch to come soon.</p>
+</div>
+<a name="N10101"></a><a name="%5BFOR-537%5D+Plugin+documentation+sitemap+references"></a>
 <h2 class="underlined_10">[FOR-537] Plugin documentation sitemap references</h2>
 <div class="section">
 <p>
@@ -631,7 +659,15 @@
 &lt;br/&gt;
 --tim</p>
 </div>
-<a name="N10101"></a><a name="%5BFOR-671%5D+Layering+error+of+HTML+headings+breaks+rest+of+the+page+w%2Fo+warning"></a>
+<a name="N1010D"></a><a name="%5BFOR-635%5D+images+not+reproduced+in+PDFs%2C+if+sources+are+in+xdocs%2Fimages+directory"></a>
+<h2 class="underlined_10">[FOR-635] images not reproduced in PDFs, if sources are in
xdocs/images directory</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-635">http://issues.apache.org/jira/browse/FOR-635</a>
+</p>
+<p>We used to enable images to be placed in the xdocs/images directory. However, now
they are intended to go in the resources/images directory instead. Both methods will work
for html pages, but  only the latter method for the PDF pages.</p>
+</div>
+<a name="N10119"></a><a name="%5BFOR-671%5D+Layering+error+of+HTML+headings+breaks+rest+of+the+page+w%2Fo+warning"></a>
 <h2 class="underlined_10">[FOR-671] Layering error of HTML headings breaks rest of
the page w/o warning</h2>
 <div class="section">
 <p>
@@ -693,27 +729,7 @@
 &lt;br/&gt;
 &amp;lt;/html&amp;gt;</p>
 </div>
-<a name="N1010D"></a><a name="%5BFOR-861%5D+Update+locationmap+docs+for+working+with+remote+files"></a>
-<h2 class="underlined_10">[FOR-861] Update locationmap docs for working with remote
files</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-861">http://issues.apache.org/jira/browse/FOR-861</a>
-</p>
-<p>The docs for retrieving content from remote locations [1] have not kept up with
Tims wonderful naming conventions for the locationmap [2]
-&lt;br/&gt;
-
-&lt;br/&gt;
-We need to update the docs to reflect the situation described in [3] (don't miss the correction
in the next message)
-&lt;br/&gt;
-
-&lt;br/&gt;
-[1] &lt;a href="http://forrest.apache.org/docs_0_80/locationmap.html#source-via-http"&gt;http://forrest.apache.org/docs_0_80/locationmap.html#source-via-http&lt;/a&gt;
-&lt;br/&gt;
-[2] &lt;a href="http://forrest.apache.org/docs_0_80/locationmap.html#namingConvention"&gt;http://forrest.apache.org/docs_0_80/locationmap.html#namingConvention&lt;/a&gt;
-&lt;br/&gt;
-[3] &lt;a href="http://marc.theaimsgroup.com/?t=114492612100001&amp;r=1&amp;w=2"&gt;http://marc.theaimsgroup.com/?t=114492612100001&amp;amp;r=1&amp;amp;w=2&lt;/a&gt;</p>
-</div>
-<a name="N10119"></a><a name="%5BFOR-731%5D+empty+linkmap.html+document%2C+side-effect+of+workaround+to+FOR-675"></a>
+<a name="N10125"></a><a name="%5BFOR-731%5D+empty+linkmap.html+document%2C+side-effect+of+workaround+to+FOR-675"></a>
 <h2 class="underlined_10">[FOR-731] empty linkmap.html document, side-effect of workaround
to FOR-675</h2>
 <div class="section">
 <p>
@@ -721,7 +737,7 @@
 </p>
 <p>The main/webapp/resources/stylesheets/linkmap-to-document.xsl has a workaround for
a side-effect to the 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="N10125"></a><a name="%5BFOR-767%5D+Forrestbot+webapp+reports+succesful+even+when+there+are+broken+links"></a>
+<a name="N10131"></a><a name="%5BFOR-767%5D+Forrestbot+webapp+reports+succesful+even+when+there+are+broken+links"></a>
 <h2 class="underlined_10">[FOR-767] Forrestbot webapp reports succesful even when there
are broken links</h2>
 <div class="section">
 <p>
@@ -738,14 +754,6 @@
 - ??
 &lt;br/&gt;
 </p>
-</div>
-<a name="N10131"></a><a name="%5BFOR-635%5D+images+not+reproduced+in+PDFs%2C+if+sources+are+in+xdocs%2Fimages+directory"></a>
-<h2 class="underlined_10">[FOR-635] images not reproduced in PDFs, if sources are in
xdocs/images directory</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-635">http://issues.apache.org/jira/browse/FOR-635</a>
-</p>
-<p>We used to enable images to be placed in the xdocs/images directory. However, now
they are intended to go in the resources/images directory instead. Both methods will work
for html pages, but  only the latter method for the PDF pages.</p>
 </div>
 </div>
 <!--+

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

Modified: forrest/site/procedures/release/How_to_release.html
URL: http://svn.apache.org/viewvc/forrest/site/procedures/release/How_to_release.html?view=diff&rev=453465&r1=453464&r2=453465
==============================================================================
--- forrest/site/procedures/release/How_to_release.html (original)
+++ forrest/site/procedures/release/How_to_release.html Thu Oct  5 19:10:48 2006
@@ -1099,10 +1099,13 @@
                 
 <li>
                     
-<p>Tag SVN by doing <span class="codefrag">'svn copy -m "Create tag forrest_xy
from release
-                            branch" \ https://svn.apache.org/repos/asf/forrest/branches/forrest_xy_branch
\
-                            https://svn.apache.org/repos/asf/forrest/tags/forrest_xy'</span>
-                        where 'xy' is a compact (without the dots) form of the version number
(e.g. 04,
+<p>Tag SVN by doing:</p>
+
+<pre class="code">svn copy -m "Create tag forrest_xy from release branch" \
+  https://svn.apache.org/repos/asf/forrest/branches/forrest_xy_branch \
+  https://svn.apache.org/repos/asf/forrest/tags/forrest_xy</pre>
+                    
+<p>where 'xy' is a compact (without the dots) form of the version number (e.g. 04,
                         041, 05).</p>
                   
 <p> See <a href="http://svn.apache.org/repos/asf/forrest/tags/">http://svn.apache.org/repos/asf/forrest/tags/</a>
@@ -1119,6 +1122,19 @@
                 
 <li>
                     
+<p>Tag the "site" SVN by doing:</p>
+
+<pre class="code">svn copy -m "Create tag forrest_xy release" \
+  https://svn.apache.org/repos/asf/forrest/site \
+  https://svn.apache.org/repos/asf/forrest/tags/forrest_xy</pre>
+                    
+<p>where 'xy' is a compact (without the dots) form of the version number (e.g. 04,
+                        041, 05).</p>
+                
+</li>
+                
+<li>
+                    
 <p>Announce the end of the code-freeze by sendung the email-template <a href="announce_end_of_code_freeze.txt">announce_end_of_code_freeze.txt</a>to
the dev
                     list.</p>
                 
@@ -1128,7 +1144,7 @@
 </div>
 
         
-<a name="N10333"></a><a name="UploadAndAnnounce"></a>
+<a name="N10344"></a><a name="UploadAndAnnounce"></a>
 <h2 class="underlined_10">Upload and announcement</h2>
 <div class="section">
 <p>In this phase we'll upload the new Release, wait for it to be available on most
mirror sites, then
@@ -1284,7 +1300,7 @@
 </div>
 
         
-<a name="N103E2"></a><a name="cleanup"></a>
+<a name="N103F3"></a><a name="cleanup"></a>
 <h2 class="underlined_10">Cleanup</h2>
 <div class="section">
 <ol>
@@ -1376,7 +1392,7 @@
 </div>
         
         
-<a name="N10430"></a><a name="conclusion"></a>
+<a name="N10441"></a><a name="conclusion"></a>
 <h2 class="underlined_10">Conclusion</h2>
 <div class="section">
 <p>All done!</p>

Modified: forrest/site/procedures/release/How_to_release.pdf
URL: http://svn.apache.org/viewvc/forrest/site/procedures/release/How_to_release.pdf?view=diff&rev=453465&r1=453464&r2=453465
==============================================================================
Binary files - no diff available.



Mime
View raw message