forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <>
Subject Re: Code cosmetics (was: [GUMP] Build Failure - xml-forrest)
Date Tue, 15 Apr 2003 15:21:19 GMT
On Tue, Apr 15, 2003 at 02:57:01PM +0200, Marc Portier wrote:
> Hi there,
> this sounds like a bit of an upcoming issue
> for a rather cosmetic change:
> (thx to Steven for helping me see the wonders of viewcvs)
> I would not like to just add the upcoming method as well and 
> delegate to the old one since then we will just shut up gump and 
> will loose his alarming function reminding us that we still have 
> to remove the old signatures some time in future, right?

That's a good idea.

> So upgrading to cocoon-head once again seems appropriate, I'm 
> getting into gear for doing the job, was just asking a number of 
> things:
> I know I have been somewhat of this list lately, but your short 
> answers can help me get the most of the effort I still want to 
> share...
> 0. have any of you tried recently and are there issues?

I tried ~2 weeks ago and failed.  Caching issues it seemed:

There is also a bug where Cocoon doesn't quit cleanly due to a rogue

On the positive side, it sounds like Carsten has just fixed the
cocoon.xconf reload bug.

> 1. do we have some minor standard procedure on how to build 
> cocoon for forrest and test it?

If you look in etc/cocoon_upgrade/, there's a diff containing changes
needed for the new cli.xconf, plus the generateKey -> getKey() code
change.  There's a shell script which will attempt to upgrade the jars

> 2. how urgent do you guys feel this is?

I don't think upgrading Cocoon is particularly urgent.  It depends on
this equation:

Net gain = bugs fixed - bugs introduced - upgrade cost

Libre stuff addressed in a separate email..


> regards,
> -marc=

View raw message