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

Jörg Schaible wrote:
> Well, it seems we're back were we started ....

Well, yes and no ... maybe ... sorta :-)

Unfortunately, as we working with Mike on finishing the m2 build and it became clear that we were up 
against the wall.

Moving from m1 to m2 did change a few subtle cards on the table:

- the WW guys have yes changed package from 1.x to 2.x but have not changed groupId - but the trick 
we used in m1 (declaring different dependencies by loading one from are relative path) does not work 
in m2 anymore.

- the transitive dependency in m2 now make it just a easy (or even easier) to use nanowar with a 
single dependency call.  Eg if I want to use nanowar with WW2, I simply declare

         <dependency>
             <groupId>org.nanocontainer</groupId>
             <artifactId>nanocontainer-nanowar-webwork2</artifactId>
         </dependency>

which know all it needs to know about the WW2-related dependencies.  Compare this with the need to 
declare

         <dependency>
             <groupId>org.nanocontainer</groupId>
             <artifactId>nanocontainer-nanowar</artifactId>
         </dependency>

         <dependency>
             <groupId>opensymphony</groupId>
             <artifactId>xwork</artifactId>
         </dependency>

         <dependency>
             <groupId>opensymphony</groupId>
             <artifactId>webwork</artifactId>
         </dependency>


etc etc ...

Typically, one uses the *one* framework of choice at a time, be it struts, WW or other.

- we can still have a m2 module - call it nanocontainer-nanowar-all - which includes all the nanowar 
modules.  Either as a simple POM that declares all the nanowar modules as dependencies or we can 
merge together the jars into a uberjar.  So the end product can still be the same, although the 
intermediate factors are not.
We can also have a distribution/assembly of all jars into a downloadable zip.

- building the examples in m2 was also much cleaner in this way.

Given the above, does anybody foresee any real problem with current setup?

Cheers



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

    http://xircles.codehaus.org/manage_email