You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Berin Loritsch <bl...@apache.org> on 2001/06/06 15:53:44 UTC
Showstopper in Excalibur 4.0b2
I would like to propose a vote to release 4.0b3 for
Avalon/Excalibur (quietly no general announcements)
due to a major bug I found in Excalibur's Component
Management framework. The bug stemmed from the
deprecation of the DefaultComponentManager/Selector
and moving to ExcaliburComponentManager/Selector.
The DefaultComponentFactory tested to see if we
have an instance of a "DefaultComponentSelector"
instead of the "ExcaliburComponentSelector". When
I migrated Cocoon to use the propper version of
the ComponentSelector, this ugly bug showed up.
I would like to test and then release Beta 3 for
Framework/Excalibur. I am updating the Change
docs now.
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
RE: Showstopper in Excalibur 4.0b2
Posted by Leo Simons <ma...@leosimons.com>.
> Peter Donald wrote:
> >
> > At 09:53 AM 6/6/01 -0400, Berin Loritsch wrote:
> > >I would like to propose a vote to release 4.0b3 for
> > >Avalon/Excalibur (quietly no general announcements)
> > >due to a major bug I found in Excalibur's Component
> > >Management framework. The bug stemmed from the
> > >deprecation of the DefaultComponentManager/Selector
> > >and moving to ExcaliburComponentManager/Selector.
> > >
> > >The DefaultComponentFactory tested to see if we
> > >have an instance of a "DefaultComponentSelector"
> > >instead of the "ExcaliburComponentSelector". When
> > >I migrated Cocoon to use the propper version of
> > >the ComponentSelector, this ugly bug showed up.
> > >
> > >
> > >I would like to test and then release Beta 3 for
> > >Framework/Excalibur. I am updating the Change
> > >docs now.
> >
> > Fine by me. I would prefer minor releases for this sort of
> thing (ie 2.1)
> > but 3 works for me aswell ;)
>
> +1 for release
> Slight preference for 4.0b3 over 4.0b2.1 but not fussed
> Charles
+1 to that.
Leo, who is going to write an avalon-based/JAMES-compatible/
Tomcat-contained webmail client for his new employer, but has lots
of problems getting them to allow an OS release...
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Showstopper in Excalibur 4.0b2
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
Peter Donald wrote:
>
> At 09:53 AM 6/6/01 -0400, Berin Loritsch wrote:
> >I would like to propose a vote to release 4.0b3 for
> >Avalon/Excalibur (quietly no general announcements)
> >due to a major bug I found in Excalibur's Component
> >Management framework. The bug stemmed from the
> >deprecation of the DefaultComponentManager/Selector
> >and moving to ExcaliburComponentManager/Selector.
> >
> >The DefaultComponentFactory tested to see if we
> >have an instance of a "DefaultComponentSelector"
> >instead of the "ExcaliburComponentSelector". When
> >I migrated Cocoon to use the propper version of
> >the ComponentSelector, this ugly bug showed up.
> >
> >
> >I would like to test and then release Beta 3 for
> >Framework/Excalibur. I am updating the Change
> >docs now.
>
> Fine by me. I would prefer minor releases for this sort of thing (ie 2.1)
> but 3 works for me aswell ;)
+1 for release
Slight preference for 4.0b3 over 4.0b2.1 but not fussed
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Showstopper in Excalibur 4.0b2
Posted by Peter Donald <do...@apache.org>.
At 09:53 AM 6/6/01 -0400, Berin Loritsch wrote:
>I would like to propose a vote to release 4.0b3 for
>Avalon/Excalibur (quietly no general announcements)
>due to a major bug I found in Excalibur's Component
>Management framework. The bug stemmed from the
>deprecation of the DefaultComponentManager/Selector
>and moving to ExcaliburComponentManager/Selector.
>
>The DefaultComponentFactory tested to see if we
>have an instance of a "DefaultComponentSelector"
>instead of the "ExcaliburComponentSelector". When
>I migrated Cocoon to use the propper version of
>the ComponentSelector, this ugly bug showed up.
>
>
>I would like to test and then release Beta 3 for
>Framework/Excalibur. I am updating the Change
>docs now.
Fine by me. I would prefer minor releases for this sort of thing (ie 2.1)
but 3 works for me aswell ;)
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org