whitespace cleanup

> Added: > forrest/trunk/site-author/content/xdocs/developer-guide.xml (with props) [ snip] > + > + Whitespace, line breaks, and tabs > + These are simple, but essential, topics for contributing to > Forrest. > + > + > +Thou shalt leave no trailing whitesp

[jira] Created: (FOR-640) investigate [ERROR] "unknown font sans,normal,normal so defaulted font to any"

investigate [ERROR] "unknown font sans,normal,normal so defaulted font to any" -- Key: FOR-640 URL: http://issues.apache.org/jira/browse/FOR-640 Project: Forrest Type: Bug Reporter: Juan

[HEAD UPS] Upgrade cocoon version and xalan

Hi guys, I am in the middle of upgrade cocoon because sylvain has added Cocoon stack traces [1] to the cocoon trunk. I notice that just only 3 new jar files needs to be updated. M core/cocoon-2.2.0-dev-r230820.jar M core/cocoon-xsp-block-2.2.0-dev-r230820.jar M core/cocoon-prof

Re: Fallback resolver Vs. Locationmap (was Re: svn commit: r233401 - in /forrest/trunk: main/webapp/ main/webapp/WEB-INF/xconf/ site-author/ whiteboard/plugins/org.apache.forrest.plugin.internal.view/

On Fri, 2005-08-19 at 09:52 +0100, Ross Gardler wrote: > [EMAIL PROTECTED] wrote: > > Author: thorsten > > Date: Thu Aug 18 17:44:00 2005 > > New Revision: 233401 > > > > ... > > > Added: > > forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.view/src/java/org/apache/forrest/pl

Re: Trimming SVN checkouts (was Re: Move eclipse tools out of trunk)

Ross Gardler wrote: > > I've not thought through the implications of this. I'm pretty sure that > moving tools out is a good idea (notice I suggest a tools subdirectory > when moving eclipse, that was for a reason ;-) feel free to rubbish the > idea though (or even agree with it ;-) I don't ye

Re: Defining Views Terminology

Ross Gardler wrote: > David Crossley wrote: > >Ross Gardler wrote: > > > >>Some of the confusion over Views seems to have come about because they > >>do much more than just replace skins. They add a whole new feature set. > >>We therefore decided to define some terminology to help clarify the > >>s

Re: Trimming SVN checkouts (was Re: Move eclipse tools out of trunk)

Diwaker Gupta wrote: > On Thursday 18 August 2005 8:21 am, Ross Gardler wrote: > > core > >/trunk > >/branches > > plugins > >/org.apache.forrest.input.wiki > > /trunk > > /branches > >/org.apache.forrest.output.pdf > > /trunk > > /branches > > tools > >/ecli

Fallback resolver Vs. Locationmap (was Re: svn commit: r233401 - in /forrest/trunk: main/webapp/ main/webapp/WEB-INF/xconf/ site-author/ whiteboard/plugins/org.apache.forrest.plugin.internal.view/ whi

[EMAIL PROTECTED] wrote: Author: thorsten Date: Thu Aug 18 17:44:00 2005 New Revision: 233401 ... Added: forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.view/src/java/org/apache/forrest/plugin/internal/view/acting/FallbackResolverAction.java Does this fallback resolver

Re: using the plugin status.xml (Was: svn commit: r233401)

Ross Gardler wrote: Thorsten Scherler wrote: On Fri, 2005-08-19 at 12:46 +1000, David Crossley wrote: I think that notes about changes like this should go into the status.xml in each plugin, and keep this top-level status for high-level notes about major changes in each plugin. Thanks for

Re: Measuring and improving Forrest build times

Ron Blaschke wrote: Thursday, August 18, 2005, 5:58:54 PM, David Crossley wrote: Ross Gardler wrote: David Crossley wrote: Ron Blaschke wrote: Thought for the future when this is sorted out. Can we create a new test target that will do this profiling for us? That way, each time we up

Re: Defining Views Terminology

David Crossley wrote: Ross Gardler wrote: [NOTE: this is my summary of my interpretation of *part* of the discussion at the views workshop at Apachecon. In other words I have tried to represent the views of those present, but may have got some bits wrong - this is a document for discussion no

Re: using the plugin status.xml (Was: svn commit: r233401)

Thorsten Scherler wrote: On Fri, 2005-08-19 at 12:46 +1000, David Crossley wrote: I think that notes about changes like this should go into the status.xml in each plugin, and keep this top-level status for high-level notes about major changes in each plugin. Thanks for bringing this up, Davi

Re: debugging views - short (was Re: [views] head broken?)

Thorsten Scherler wrote: Last night I got (for this project): java.lang.RuntimeException: ElemTemplateElement error: Found more than one template named: navigation-link-index-content The improved error reporting I noted earlier has now gone into Cocoon 2.2 I've been using it in 2.1.8-dev recen

Re: [Views] [HEADSUP] Code refactoring

On Fri, 2005-08-19 at 16:07 +1000, David Crossley wrote: > Ah, that is uncommented now and all is well. > I had assumed that the project.skin was redundant now, > but not so. No, still not. I reckon we should extend the internal.view with *all* skining pipes and force there to use leather-dev.

Re: using the plugin status.xml (Was: svn commit: r233401)

On Fri, 2005-08-19 at 12:46 +1000, David Crossley wrote: > I think that notes about changes like this should go into > the status.xml in each plugin, and keep this top-level > status for high-level notes about major changes in > each plugin. Thanks for bringing this up, David. In general I agree

Re: Trimming SVN checkouts (was Re: Move eclipse tools out of trunk)

On Thursday 18 August 2005 8:21 am, Ross Gardler wrote: > core >/trunk >/branches > plugins >/org.apache.forrest.input.wiki > /trunk > /branches >/org.apache.forrest.output.pdf > /trunk > /branches > tools >/eclipse > /trunk > /branches >/forres