Farr, Aaron wrote:
Some things seem obvious to me, like composition and activation should go
with Merlin. But what about repository? It's actually an independent tool,
and a rather nice one. Should it go with Merlin? Stay in Avalon? Go to
the depot group? And what about meta? The implementation should probably
go to Merlin but will we at least have a unified set of meta-tags? And the
new avalon-logging? Should it stay in Avalon or move with Merlin?
Repository is not directly related to components--only indirectly. So
it shouldn't remain in Avalon. The only two options would be to send it
with Merlin or send it to commons.
Meta? Never really liked it, but I am not going to rehash it. As it is
currently written, it will cause major issues if we change parts of it
as Merlin depends on it. The spec for the tags remains with Avalon, but
the library for Merlin should stay with Merlin.
I'm not saying we have to answer these questions now before we make a
decision. I just want to point out that there would be plenty of details to
work out. The issues are really there regardless of it being Fortress or
Merlin which is promoted.
Obviously. However, what is left in Avalon? If Merlin leaves, we have
some components, a framework, a couple old containers, and a battered
community. The biggest thing to address is how to keep life in Avalon
after Merlin moves out.
What about Leo's proposal? What does the Leo Gang of Nine think?
I dunno about the nine, but I have a protection of assets to think
about. Since my Dojo container works pretty well for my needs, I am
going to improve on it and make it my official container for GUIApp.
I am not aware of a lot of third party components being written for it,
but supporting Avalon components will be important.
After some initial experiments, I can provide some guidance on choosing
or adapting meta tags to be future compatible with Java 1.5. But I
haven't gotten that far yet.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
