On Sat, 2004-01-17 at 17:12, Stephen McConnell wrote:
> It's a starting point - and I figure the sooner we start the sooner we
> will have a better idea about the real overhead concerning potential
> changes.
I like your suggestions.
Many of us feel that avalon-excalibur could eventually be dissolved into
Avalon Components (Cornerstone) and a set of Avalon utilities (probably
held under the avalon CVS module). But doing so will not be easy due to
the amount of legacy support needed. For example, Cocoon committers
have access to excalibur and will be equally interested in its future.
So, we're now looking at:
Category: Avalon
avalon-framework
avalon-extension
avalon-meta
avalon-util
avalon-repository
avalon-site <-- or should site be a component somewhere?
Fortress
Phoenix
Logkit
Excalibur <-- at least to start. Perhaps will expand or
disappear completely
Category: Avalon Components
cornerstone-connection
cornerstone-datasources
cornerstone-scheduler
cornerstone-sockets
cornerstone-store
cornerstone-threads
Category: Avalon Merlin
avalon-composition
avalon-activation
merlin
merlin-http
merlin-jmx
Yeah, this looks much more reasonable.
--
jaaron <http://jadetower.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
