Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Date: Fri, 16 Sep 2005 01:45:54 +1000
From: David Crossley <crossley@apache.org>
To: dev@forrest.apache.org
Subject: Re: JX in forrest
Message-ID: <20050915154554.GA13899@igg.indexgeo.com.au>
References: <1126448615.6496.0.camel@localhost.localdomain>
 <1126512336.5078.20.camel@localhost.localdomain> <43256F27.407@apache.org>
 <1126657024.4917.67.camel@localhost.localdomain>
 <20050914004103.GA6494@igg.indexgeo.com.au>
 <1126659739.4917.93.camel@localhost.localdomain> <dg8hqu$1bf$2@sea.gmane.org>
 <1126736430.21056.7.camel@localhost.localdomain>
 <20050915000617.GB10840@igg.indexgeo.com.au>
 <1126772475.5125.15.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1126772475.5125.15.camel@localhost.localdomain>
User-Agent: Mutt/1.4i

Thorsten Scherler wrote:
> David Crossley wrote:
> > Thorsten Scherler wrote:
> > > Nicola Ken Barozzi wrote:
> > > > Thorsten Scherler wrote:
> > > > ...
> > > > > Why do we have our own xconf that we need to keep in sync with the
> > > > > cocoon one? 
> > > > 
> > > > Because we tweak it as needed.
> > > 
> > > That should be done via xpatch and not by hand. Tweaking makes
> > > maintainment hard. 
> > 
> > Cocoon is moving away from using xpatch. In fact lots of that
> > is already implemented in Cocoon trunk. We need to change
> > our way of handling xconf and sitemap snippets.
> 
> Yeah they do not use xpath but include a dir with conf-snippets which is
> even better.

This would be a good time for us to review all
of our cocoon configuration. Yes it will be easier now.

I wonder if that is why we suddenly had problems
with 'forrest site' taking three times as long
following the previous Cocoon upgrade. Maybe there 
is some configuration change that we have missed.

> > > > > Why not just patching the cocoon one and using the original cocoon
> > > > > version of xconf, sitemaps, etc.?
> > > > 
> > > > Because the Cocoon ones are an example/template for Cocoon, not to be
> > > > used in production.
> > > 
> > > The xconf as well?
> > 
> > Yes.
> 
> We are as well using this. We made our own xconf based on this example
> but still...
> 
> > > BTW I finally got it working after a chat with Antonio. He brought me on
> > > the right track. Thx Antonio.
> > 
> > It would be better to talk on the list. Antonio is subscribed.
> > Then we might all be able to assist.
> 
> In general you are right, but not in this case.
> 
> I do not see the point in having *private* conversions with Antonio,
> which is a friend, here on the list. We did *not* talked about this
> issue, it was covered only in one sentence, it was a *private* chat. 

Not what i meant. If you think that you solved
something that has plauged us for such a long time,
then it would be good to hear the answer. Obviously
it is not quite working, and perhaps other people
can help.

Sorry that my comment came across badly.

> > Anyway, not so. Did you run 'build test' after making
> > such a drastic change?
> 
> No sorry, I only tested the dynamic mode. Will be more careful in the
> future.

Thanks. We decided a while ago to try to not
bust the trunk and agreed to do 'build test'.

It really is time to work more on our 
forrest.zones.apache.org so that it can send
email when something breaks.

> I removed the offending lib again. BTW you have write access as well,
> right? 

That would make the fourth time that i have
needed to roll back that commit.

Anyway i regret reacting. Sorry about that.

-David