-----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Leo Simons
Stephen McConnell wrote:
avalon-framework-api
avalon-framework-spi <-- contains MutableConfiguration avalon-framework-impl <-- depends on spi and api
IMHO avalon-framework-impl =~ avalon-framework-spi. It only contains stuff useful to containers implementing framework support. Yet-another-jar-with-only-5-classes doesn't seem like a good idea, especially as the split classloader argument doesn't seem to hold here.
I agree with this. Currently, that jar would have *one* class - MutableConfiguration.
Yes - I aware of the "one class" point which is partly why I initially suggested that we address this separately under an avalon-configuration (specifically moving the issue away from the framework and incorporating resolution with excalibur-configuration).
My two proposals are:
(a) use framework-spi
(b) or setup an avalon/avalon-configuration subproject
containing api and impl packages (and include in this
process rationalization of the excalibur-configuration
content)Please note that neither of these proposals impact the framework API explicitly or implicitly), and at the same time ensure that viable solutions are available so that you are not blocked in terms of moving forward.
Personally I would prefer to see option (b) as the sensible solution because this addresses the broader question of the non-component content in the excalibur-configuration package that IMO should be incorporated into a single sub-project. Another alternative is to simply do this under the existing excalibur-configuration package.
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]
