Welcome.
It would be a lot easier to just put the new classes in the same jars as the impls :-) We've done some poking and it is very easy to make these classes.1) it surely makes sense to automate this (but, maybe we shall do that tomorrow and use hand-craft today? :-)
2) if this is a separate class, should we packages it
* in the main jar
* in an additional jar
if we choose additional, then we shall save even those
tiny kb that would otherwise be added
Nope. The more inter-component compatbility the better :-) Components are far more important IMHO.I don't think you need to worry about Avalon users using the constructor directly.
LS> my thought was about people that use neither pico nor avalon but just LS> need a reusable bean. One of the good things about pico is that you're LS> also making that a real possibility, innit?
Truly speaking, I think it going to be great! Probably we're approaching one step closer to the KISS idiom :) I think we all feel a fresh wind blowing from Pico :-)
And the more inter-container compatibility the better :-))
It is only the components I see as shared between Pico/Nano containers over at Codehaus and Avalon's various containers.
- Paul
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
