On Sat, 2004-01-17 at 19:02, Stephen McConnell wrote:
The JIRA people must have been thinking about this before and during development, since IMHO
Category = Avalon
Product = Cornerstone
Component = Cornerstone Datasources
So this is basically the aggregated approach listed. Other components would include things like Documentation and Test coverage.
Instead ... I'm thinking along the following lines:
Category = Avalon Components Product = Cornerstone Datasources Component = Documentation
I've been burning out a few brain cells myself on this one too. :) Seeing the exact list of project helps me understand the situation
better. So under this setup we have:
Category: Avalon avalon-framework avalon-extension
The avalon-extension package is currently under the Merlin tree but really needs to move to Avalon level because:
(a) its future relationship to the repository package
(related to classloader construction).
(b) its not a componentavalon-meta avalon-composition avalon-activation
I suggest we keep avalon-composition and avalon-activation under a Merlin category for now.
avalon-util avalon-plugin
The avalon-plugin should be handled as a "component" of the avalon-util product.
avalon-repository avalon-site <-- for site-wide documentation. Fortress Phoenix Logkit
Category: Avalon Components
cornerstone-connection cornerstone-datasources cornerstone-scheduler cornerstone-sockets cornerstone-store cornerstone-threads
Category: Avalon Excalibur (should this be combined with Components?)
I don't think we should do this as sweeping move. Instead I would keep Avalon Excalibur as a category and deal with changes on a step by step basis as the respective products evolve.
excalibur-compatibility
This one could/should go under a new Avalon Archive category.
excalibur-configuration
Recommend moving excalibur-configuration to avalon-util.
excalibur-datasource excalibur-event excalibur-i18n
Recommend moving excalibur-i18n to avalon-util.
excalibur-instrument excalibur-lifecycle
Should move to avalon category.
excalibur-logger excalibur-monitor excalibur-naming excalibur-pool excalibur-sourceresolve excalibur-thread
I intentionally left Merlin out. Not sure if it would be a category or single project. Under this scheme I could see it going either way.
Here is the breakdown for a Merlin Category.
Category: Avalon Merlin
Product: avalon-composition
Product: avalon-activation
Product: merlin
Product: merlin-http
Product: merlin-jmxThis seems much more reasonable. Still a little uneasy about components coming and going. Several of these Excalibur components could disappear this next year, being merged into a cornerstone equivalent, sent to jakarta-commons, or just deprecated. This, more than anything else, is really my concern about such an approach. And more so with Excalibur than anything else too.
Yep - its a headache.
Maybe we could initially have just one for excalibur and have everything else as listed above. At least until we have a better feel for these component's future.
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.
Cheers, Steve.
--
|------------------------------------------------| | 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]
