[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Breaking up the MC project and Mavenizing it

[scott.stark@jboss.org]

My thougts are that we need to transform the existing jbossbuild projects under:
https://svn.jboss.org/repos/jbossas/projects/microcontainer/trunk/

into a maven based build, and break up the container project in the process as its jboss-container.jar artifact is too coarse. At a minimum, it should probably be broken up into projects for the following packages:

P1
org.jboss.classloading

P2:
org.jboss.metadata
org.jboss.repository - maybe should be dropped as metadata is replacing it

P3:
org.jboss.net
org.jboss.virtual - VFS code

P4:
org.jboss.annotation
org.jboss.beans
org.jboss.classadaptor
org.jboss.config
org.jboss.joinpoint
org.jboss.reflect


Every project should be further broken up into an spi/api artifacts for the spi packages, and a plugin artifact for the plugin/implementation packages.

The aspects in the aop-mc-int project should be in a separate common aspects project. 


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990814#3990814

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990814