Just as a matter of preference, I don't think calling it a 'serious bug
fix' was helpful for Avalon or necessary.
Especially given the closeness to the beta2. Something like "This
release is solely a bug fix for ExcalibutComponentSelector" would have
been sufficient.
Cheers,
Charles
Berin Loritsch wrote:
>
> The Avalon team announces the beta 3 release of Avalon
> Framework and Excalibur 4.0. This release includes a serious
> bug fix in Excalibur's Component Management infrastructure.
> If you have downloaded Avalon 4.0 beta 2, then you are
> encouraged to upgrade. The bug only affects users of the
> ExcaliburComponentSelector.
>
> Avalon
> ------
> http://jakarta.apache.org/avalon
>
> The Avalon project is Apache's Java Server Framework. It is
> separated into six sub projects: Framework, Excalibur, LogKit,
> Cornerstone, Phoenix, and Testlet. It's purpose is to simplify
> server side programming for Java based projects. It
> formalizes serveral best of breed practices and patterns for
> server side programming.
>
> Avalon Framework 4.0 beta 3
> ---------------------------
> http://jakarta.apache.org/avalon/framework
>
> Avalon Framework is the core of all of the Avalon projects,
> and formalizes all the contracts and patterns used within all
> Avalon compliant projects.
>
> Avalon Excalibur 4.0 beta 3
> ---------------------------
> http://jakarta.apache.org/avalon/excalibur
>
> Avalon Excalibur contains several premade Avalon Components
> and utilities to make your server side programming easier.
> There are several pool implementations, Component management
> implamentations, and database management implementations.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
