Leo Sutic wrote:
> Berin and other committers,
>
> how is the release for Excalibur 4.1 coming along? Cocoon is up for a 2.0.1
> release soon and it would be good to get Framework 4.1.1 and Excalibur 4.1
> in that release.
I was on the fast track, and got sidetracked. I appologize.
OK crew, what remains to be done for Excalibur 4.1 final release?
If we can't think of anything, lets wrap this puppy up and send it out. The
stuff in scratchpad will have to stay as it is (as long as it compiles).
> Why? Well, logging is broken on my system due to class loader issues with
> Excalibur 4.0. So I need 4.1 to get logging in Cocoon. But Cocoon will not
> compile with the current CVS version of Excalibur since the PriorityQueue
> interface changed. I have a patch for that, but before I can have it applied
> to Cocoon, I need to convince the Cocooners to upgrade to Excalibur 4.1.
> Which doesn't exist.
They have a CVS version in HEAD of the current Excalibur now.
> Forking is, of course, the short-term solution. But I'd rather get the stuff
> I want changed into the main distribution.
I hear you.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
