You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Leo Sutic <le...@inspireinfrastructure.com> on 2002/01/24 20:28:50 UTC
Excalibur 4.1 release
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.
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.
Phew...
Forking is, of course, the short-term solution. But I'd rather get the stuff
I want changed into the main distribution.
/LS
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Excalibur 4.1 release
Posted by Peter Donald <pe...@apache.org>.
On Fri, 25 Jan 2002 18:26, Jeremias Maerki wrote:
> > OK crew, what remains to be done for Excalibur 4.1 final release?
>
> I'm still hoping my patch (14.01.2002, Re: Logging in Avalon:
> CascadingThrowable and getTime/GetRTime in LogKit) could be
> committed before the release. I believe it might be necessary to make a
> release of Framework, too, because the AvalonFormatter was already
> changed a bit and Excalibur logging stuff has dependencies on it.
Could you repost it I can't seem to find the patch.
--
Cheers,
Pete
--------------------------------------------
Beer is proof that God loves us and wants
us to be happy. -- Benjamin Franklin
--------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Excalibur 4.1 release
Posted by Jeremias Maerki <je...@outline.ch>.
> OK crew, what remains to be done for Excalibur 4.1 final release?
I'm still hoping my patch (14.01.2002, Re: Logging in Avalon:
CascadingThrowable and getTime/GetRTime in LogKit) could be
committed before the release. I believe it might be necessary to make a
release of Framework, too, because the AvalonFormatter was already
changed a bit and Excalibur logging stuff has dependencies on it.
Cheers
Jeremias Märki
mailto:jeremias.maerki@outline.ch
OUTLINE AG
Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern
Fon +41 (41) 317 2020 - Fax +41 (41) 317 2029
Internet http://www.outline.ch
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Excalibur 4.1 release
Posted by Berin Loritsch <bl...@apache.org>.
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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>