Aaron Farr wrote:
-----Original Message----- From: Niclas Hedhman [mailto:[EMAIL PROTECTED]
I also don't understand the ever raised "supporting existing ECM users", since there hasn't been any 'support' worth the
name as long
as I have been around
(1 year+), and we are not talking about deleting the content, so... What does these words actually mean "supporting existing users" ?
It's not ECM. ECM is deprecated. Excalibur is not. Excalibur is more than just ECM. There are components in Excalibur [1] which have been officially released just like the Cornerstone components. It is the support and future of these components with which I am concerned.
A long time ago we decided (and voted) to move the excalibur components to avalon-components as soon as they have been officially released. So perhaps it's time now to remember this and move the components?
Keep in mind that before moving anything over to avalon-components - bringing respective packages in line with a common component model will be a prerequisite.
In particular:
1. usage of standard avalon meta tags 2. elimination of fortress specific context dependencies 3. resolution of components using /Selector semantics
Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
