Re: [picocontainer-dev] FW: [picocontainer] [3121] java/nanocontainer-nanowar/trunk: Split nanowar into core and separate modules for each framework supported.

Mauro Talevi wrote:
> Konstantin Priblouda wrote:
>> --- Jörg Schaible <[email protected]>
>> wrote:
>>
>>> Well, how often do you use two of those at same
>>> time? 
>>
>> never ;)
>>
>>> And if you do, then it is no problem to
>>> declare two deps ... or?
>>
>> with m2 this is not even that - transient dependencies
>> rule ;)
>> placing everything is single project would lead (
>> under m2 ) to additional unnecessary dependencies,
>> landing automatically in war. ( to other frameworks )
>> ok, this can be prevented by making them optional, but
>> then users must declare them again ( though they
>> usually would declare such framework dependency anyway )
>
> Ok - seems there is consensus then:  if no one objects as part of the 
> move to m2, I'll then start splitting the nanocontainer modules as well.
>
> The core-core + one module per scripting language + an AOP module?
> Perhaps the XML should be left as default in core.

I agree... the XML can be done without all the optional dependencies, so 
if you are going to split it, lets keep it as simple as possible for 
newbies to get going.

                                     -Mike



---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email