Return-Path: Delivered-To: apmail-forrest-svn-archive@www.apache.org Received: (qmail 29124 invoked from network); 6 Oct 2006 02:10:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Oct 2006 02:10:59 -0000 Received: (qmail 18694 invoked by uid 500); 6 Oct 2006 02:10:59 -0000 Delivered-To: apmail-forrest-svn-archive@forrest.apache.org Received: (qmail 18639 invoked by uid 500); 6 Oct 2006 02:10:59 -0000 Mailing-List: contact svn-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Forrest Developers List" List-Id: Delivered-To: mailing list svn@forrest.apache.org Received: (qmail 18628 invoked by uid 99); 6 Oct 2006 02:10:57 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Oct 2006 19:10:57 -0700 X-ASF-Spam-Status: No, hits=-9.4 required=5.0 tests=ALL_TRUSTED,NO_REAL_NAME Received: from [140.211.166.113] ([140.211.166.113:61467] helo=eris.apache.org) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id 14/B0-04543-C2BB5254 for ; Thu, 05 Oct 2006 19:10:52 -0700 Received: by eris.apache.org (Postfix, from userid 65534) id CBB9D1A981A; Thu, 5 Oct 2006 19:10:49 -0700 (PDT) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit 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 -0000 To: svn@forrest.apache.org From: crossley@apache.org X-Mailer: svnmailer-1.1.0 Message-Id: <20061006021049.CBB9D1A981A@eris.apache.org> X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N 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 @@
  • ApacheCon US 2006 (9-13 October 2006) +
  • @@ -307,13 +312,24 @@ - Please make plans to join us for the conference in Austin, Texas, USA on 9-13 October 2006.

    +

    + Apart from all of the general ApacheCon events, there are a number of + Forrest-specific events. In chronological order ... +

    + +

    ApacheCon Session: WE21: Single Source Publishing with Apache Forrest

    +

    + Wednesday 11 October - Official ApacheCon session + conducted by Ferdinand Soethe. + Read more. +

    - +

    Past events

    - +

    ApacheCon EU 2006 (26-30 June)

    @@ -325,7 +341,7 @@ Apart from all of the general ApacheCon events, there are a number of Forrest-specific events. In chronological order ...

    - +

    ApacheCon Session: FR19: Single Source Publishing with Apache Forrest

    Friday 30 June - Official ApacheCon session @@ -337,7 +353,7 @@

    Note
    This session is has been re-scheduled for Friday 30 June 14:30-15:30.
    - +

    ApacheCon US 2005 (10-14 December)

    @@ -348,7 +364,7 @@ Apart from all of the general ApacheCon events, there is one Forrest-specific event.

    - +

    ApacheCon Session: Single Source Publishing with Apache Forrest

    Tuesday 13 December at 09:00 to 10:00 - Official ApacheCon session @@ -357,7 +373,7 @@ Schedule Session TU01. The event is only open to ApacheCon attendees.

    - +

    ApacheCon Europe 2005 (18-22 July)

    @@ -369,7 +385,7 @@ Apart from all of the general ApacheCon events, there are a number of Forrest-specific events. In chronological order ...

    - +

    Apache committers hackathon

    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.

    - +

    Apache Forrest workshop on Views

    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.

    - +

    Usability professionals meeting

    Tuesday 19 July commencing at 18:30 - Johannes Schaefer will @@ -399,7 +415,7 @@ See further information.

    - +

    ApacheCon Session: Single Source Publishing with Apache Forrest

    Wednesday 20 July at 14:30 to 15:30 - Official ApacheCon session @@ -408,7 +424,7 @@ Schedule Session WE16. The event is only open to ApacheCon attendees.

    - +

    Apache Forrest get-together

    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 @@

    @@ -273,15 +273,7 @@ all open issues). The listing below is regenerated on each Forrest run.
    - -

    [FOR-868] add relevant notes to the "Upgrading" xdoc

    -
    -

    -http://issues.apache.org/jira/browse/FOR-868 -

    -

    We need to add some notes to the upgrading_0*.html doc for the upcoming release. This would most easily be done after attending to <a href="http://issues.apache.org/jira/browse/FOR-865" title="Add missing entries to status.xml to generate the changes list">FOR-865</a> &quot;Add missing entries to status.xml to generate the changes list&quot;.

    -
    - +

    [FOR-855] verify the license situation prior to each release

    @@ -303,7 +295,7 @@ <br/>

    - +

    [FOR-865] Add missing entries to status.xml to generate the changes list

    @@ -321,39 +313,31 @@ <br/> <a href="http://marc.theaimsgroup.com/?t=114274836600001">http://marc.theaimsgroup.com/?t=114274836600001</a>

    - -

    [FOR-735] Plugins are not correctly deployed in webapp mode

    + +

    [FOR-868] add relevant notes to the "Upgrading" xdoc

    -http://issues.apache.org/jira/browse/FOR-735 +http://issues.apache.org/jira/browse/FOR-868

    -

    (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) -<br/> - -<br/> -- run forrest webapp to create an empty webapp -<br/> -- configure Tomcat to run the webapp (we did it by creating a context descriptor and put it onder Tomcat's config directory) -<br/> -- the pdf links give an error &quot;Resource Not Found&quot;

    +

    We need to add some notes to the upgrading_0*.html doc for the upcoming release. This would most easily be done after attending to <a href="http://issues.apache.org/jira/browse/FOR-865" title="Add missing entries to status.xml to generate the changes list">FOR-865</a> &quot;Add missing entries to status.xml to generate the changes list&quot;.

    - -

    [FOR-711] Cache results from the Locationmap

    + +

    [FOR-533] Auto Generate plugins.xml entry

    -http://issues.apache.org/jira/browse/FOR-711 +http://issues.apache.org/jira/browse/FOR-533

    -

    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. +

    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. <br/> <br/> -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. <br/> <br/> -If we test all locationmaps and find no result we should record that tere is no result in this hashmap. This will also be a good place to throw an exception so that Cocoon can better report such errors (see <a href="http://issues.apache.org/jira/browse/FOR-701" title="Missing locationmap entry gives poor error">FOR-701</a>)

    +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

    - +

    [FOR-639] define terminology for the various aspects of Dispatcher

    @@ -365,35 +349,51 @@ <br/>

    - -

    [FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo

    + +

    [FOR-735] Plugins are not correctly deployed in webapp mode

    -http://issues.apache.org/jira/browse/FOR-742 +http://issues.apache.org/jira/browse/FOR-735

    -

    The plugin retrieval and deployment process are not quite correct. Recently the projectInfo plugin had its version number incremented and the &quot;unversioned&quot; plugin now relates specifically to 0.8-dev version. That prevents 0.7 from accessing the relevant plugin. +

    (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) <br/> <br/> -The solution is discussed here: +- run forrest webapp to create an empty webapp <br/> -<a href="http://marc.theaimsgroup.com/?t=113176328300002">http://marc.theaimsgroup.com/?t=113176328300002</a>

    +- configure Tomcat to run the webapp (we did it by creating a context descriptor and put it onder Tomcat's config directory) +<br/> +- the pdf links give an error &quot;Resource Not Found&quot;

    - -

    [FOR-533] Auto Generate plugins.xml entry

    + +

    [FOR-711] Cache results from the Locationmap

    -http://issues.apache.org/jira/browse/FOR-533 +http://issues.apache.org/jira/browse/FOR-711

    -

    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. +

    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. <br/> <br/> -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. <br/> <br/> -This change will require that the plugins.xml file be retrieved from the build directory rather than the plugins directory when building the plugin documentation pages. We will therefore need a fall back to retrieve this file from the network if it is not currently available - this can be done with the locationmap

    +If we test all locationmaps and find no result we should record that tere is no result in this hashmap. This will also be a good place to throw an exception so that Cocoon can better report such errors (see <a href="http://issues.apache.org/jira/browse/FOR-701" title="Missing locationmap entry gives poor error">FOR-701</a>)

    +
    + +

    [FOR-742] trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo

    +
    +

    +http://issues.apache.org/jira/browse/FOR-742 +

    +

    The plugin retrieval and deployment process are not quite correct. Recently the projectInfo plugin had its version number incremented and the &quot;unversioned&quot; plugin now relates specifically to 0.8-dev version. That prevents 0.7 from accessing the relevant plugin. +<br/> + +<br/> +The solution is discussed here: +<br/> +<a href="http://marc.theaimsgroup.com/?t=113176328300002">http://marc.theaimsgroup.com/?t=113176328300002</a>

    [FOR-241] character entities (e.g. ampersand) are expanded again for href or src attributes

    @@ -441,7 +441,19 @@ <br/> the ampersand in the link href attribute is not.

    - + +

    [FOR-200] Locationmap for Forrest and Users

    +
    +

    +http://issues.apache.org/jira/browse/FOR-200 +

    +

    The locationmap gives us the ability to specify where sources are, both for Forrest and for the users. +<br/> + +<br/> +Beware that it will not work for raw files that are not linked, as this &quot;feature&quot; currently uses a fixed dir being being copied by Ant.

    +
    +

    [FOR-546] Sitemap reference doc should be updated to reflect plugin architecture

    @@ -473,7 +485,7 @@ <br/> I found out about this because my sitemap uses the fo2pdf too (docbook to PDF), and had to add the serializer.

    - +

    [FOR-666] clarify the sitemap matches etc. in FAQ about non-skinned html

    @@ -489,7 +501,7 @@ <br/> &lt;map:match pattern=&quot;old_site/**.html&quot;&gt;

    - +

    [FOR-726] use locationmap in all of the plugins

    @@ -501,7 +513,7 @@ <br/> (Perhaps we need Jira sub-tasks for each plugin.)

    - +

    [FOR-765] forrest war gets NoSuchMethodError for some core transformer

    @@ -509,7 +521,7 @@

    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'.

    - +

    [FOR-776] rationalise the pluginTemplate and current plugins to have minimal configuration files, etc.

    @@ -539,7 +551,7 @@ <br/> Tidy up the pluginTempate/status.xml

    - +

    [FOR-901] Review the note on the home page about first forrest run and retrieving plugins from network

    @@ -549,18 +561,6 @@ <br/> <a href="http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/index.xml?r1=365495&r2=365494&pathrev=365495">http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/index.xml?r1=365495&amp;r2=365494&amp;pathrev=365495</a>

    - -

    [FOR-200] Locationmap for Forrest and Users

    -
    -

    -http://issues.apache.org/jira/browse/FOR-200 -

    -

    The locationmap gives us the ability to specify where sources are, both for Forrest and for the users. -<br/> - -<br/> -Beware that it will not work for raw files that are not linked, as this &quot;feature&quot; currently uses a fixed dir being being copied by Ant.

    -

    [FOR-906] locationmap documentation explain this-to-that.xsl naming convention and default lm matches

    @@ -601,7 +601,35 @@ <br/> These changes need to be reflected in the current docs.

    - + +

    [FOR-936] Forrest "looses" the locale when switching pages

    +
    +

    +http://issues.apache.org/jira/browse/FOR-936 +

    +

    When moving from one page to another and switching locales in between, the chosen locale is lost when entering the new page. To reproduce: +<br/> + +<br/> +1) set up and run forrest with i18n ON +<br/> +2) open a localized page +<br/> +3) switch locale by appending '?locale=XY' in the address field +<br/> +4) open another page available in both the original locale (before the switch) and the new locale XY +<br/> +5) notice how the new page is displayed in the original locale, NOT the expected XY locale +<br/> + +<br/> +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 &quot;sticky&quot; once changed - it should not change back by itself. Thus, the &quot;sticky&quot; behaviour should be default in Forrest. +<br/> + +<br/> +The fix is simple, patch to come soon.

    +
    +

    [FOR-537] Plugin documentation sitemap references

    @@ -631,7 +659,15 @@ <br/> --tim

    - + +

    [FOR-635] images not reproduced in PDFs, if sources are in xdocs/images directory

    +
    +

    +http://issues.apache.org/jira/browse/FOR-635 +

    +

    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.

    +
    +

    [FOR-671] Layering error of HTML headings breaks rest of the page w/o warning

    @@ -693,27 +729,7 @@ <br/> &lt;/html&gt;

    - -

    [FOR-861] Update locationmap docs for working with remote files

    -
    -

    -http://issues.apache.org/jira/browse/FOR-861 -

    -

    The docs for retrieving content from remote locations [1] have not kept up with Tims wonderful naming conventions for the locationmap [2] -<br/> - -<br/> -We need to update the docs to reflect the situation described in [3] (don't miss the correction in the next message) -<br/> - -<br/> -[1] <a href="http://forrest.apache.org/docs_0_80/locationmap.html#source-via-http">http://forrest.apache.org/docs_0_80/locationmap.html#source-via-http</a> -<br/> -[2] <a href="http://forrest.apache.org/docs_0_80/locationmap.html#namingConvention">http://forrest.apache.org/docs_0_80/locationmap.html#namingConvention</a> -<br/> -[3] <a href="http://marc.theaimsgroup.com/?t=114492612100001&r=1&w=2">http://marc.theaimsgroup.com/?t=114492612100001&amp;r=1&amp;w=2</a>

    -
    - +

    [FOR-731] empty linkmap.html document, side-effect of workaround to FOR-675

    @@ -721,7 +737,7 @@

    The main/webapp/resources/stylesheets/linkmap-to-document.xsl has a workaround for a side-effect to the of the workaround for issue <a href="http://issues.apache.org/jira/browse/FOR-675" title="upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc.">FOR-675</a>.

    - +

    [FOR-767] Forrestbot webapp reports succesful even when there are broken links

    @@ -738,14 +754,6 @@ - ?? <br/>

    -
    - -

    [FOR-635] images not reproduced in PDFs, if sources are in xdocs/images directory

    -
    -

    -http://issues.apache.org/jira/browse/FOR-635 -

    -

    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.