[EMAIL PROTECTED]: Project forrest (in module forrest) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project forrest has an issue affecting its community integration. This issue affects 1

[EMAIL PROTECTED]: Project forrest-test (in module forrest) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project forrest-test has an issue affecting its community integration. This issue

[jira] Subscription: FOR-open-with-patch

Issue Subscription Filter: FOR-open-with-patch (7 issues) Subscriber: rgardler Key Summary FOR-811 shine and polish the pelt theme so that it closely resembles the pelt skin http://issues.apache.org/jira/browse/FOR-811 FOR-795 Navigation bars for easy access in long

Re: svn commit: r395881 - in /forrest/trunk: main/forrest.build.xml main/targets/plugins.xml main/var/pluginlist2fetch.xsl plugins/build.xml

El vie, 21-04-2006 a las 13:44 +, [EMAIL PROTECTED] escribió: Author: cdupoirieux Date: Fri Apr 21 06:44:42 2006 New Revision: 395881 URL: http://svn.apache.org/viewcvs?rev=395881view=rev Log: FOR-747, FOR-388, FOR-343... New Plugin Fetch method to auto update plugins. I will close

upgrading Cocoon and supporting libs (Was: FOR-591)

Definitely please do upgrade our Cocoon. Our process in $FORREST_HOME/etc/cocoon_upgrade/ is way out-of-date but the principles will be similar. Even without some fix for FOR-591, we probably still need to upgrade. It has been a long time. See $FORREST_HOME/lib/core for the Cocoon blocks that we

Forrest Friday - 12 May 2006

I will be around this Friday, so i will take on the job of co-ordinator. Only 4 days to go. 12 May starting at 06:00 Greenwich Mean Time. See the calendar for your time zone. http://forrest.apache.org/forrest-friday.html We will use conventional IRC. The main communication medium is still the

[jira] Created: (FOR-877) does our .htaccess file still need AddDefaultCharset UTF-8

does our .htaccess file still need AddDefaultCharset UTF-8 -- Key: FOR-877 URL: http://issues.apache.org/jira/browse/FOR-877 Project: Forrest Type: Task Components: Documentation and website Reporter:

Re: Forrest Friday - 12 May 2006

On 5/7/06, David Crossley [EMAIL PROTECTED] wrote: I will be around this Friday, so i will take on the job of co-ordinator. Only 4 days to go. 12 May starting at 06:00 Greenwich Mean Time. See the calendar for your time zone. http://forrest.apache.org/forrest-friday.html We will use

Re: [jira] Commented: (FOR-848) upgrade NoteTaking plugin to use current Dispatcher

Ross Gardler wrote: Gav wrote: I am working on this and am making some progress. The plugin has now been converted to use current Dispatcher. I still need to get a 'notes' example working however. Rather than waffle on in Jira I'll extend this here. I see this is in the 0.8-dev