Berin Loritsch wrote:
In order to get Excalibur Component out the door, which shares many of
the utils that Fortress uses, we need to get the following projects
released immediately following Framework:
Instrument
Instrument-Manager
Logger
Pool
i18n
AltRMI
So far, Pool, I18N, and Logger have been released before. Instrument
and Instrument Manager are both things that need an initial release.
I would like to take some time to go through instrument and do "QA".
We have a soft dependency on AltRMI, so we can opt to push that
release later if necessary. Paul how do you feel about getting
an AltRMI release out?
it looks like AltRMI is indeed getting a new home @ incubator
(whoohooh!). In the light of that, I suggest we don't release any altrmi
packages with a status other than alpha.
We cannot mark Component as deprecated until Fortress is released.
When Fortress is released, we should also release a new ECM where all
the classes are deprecated in favor of the Fortress version.
+1. Which no-one will ever use of course ;)
We should also put out one last fully deprecated release of
Excalibur Concurrent and Excalibur Collections.
but these are not needed by ECM right? So we do those in Phase II or III?
Those JARs will be
there to provide binary compatibility for folks like Cocoon who have
clients that have been using the old stuff. The fully deprecated
version motivates them to use the properly maintained libraries.
+1.
cheers,
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
