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

[alesj]

A quick overview of our current MC codebase:

Microcontainer's artifacts (via Maven):

 * aop-int
 ** no SPI
 ** impl (+ resources/schema)
 *** org.jboss.aop.microcontainer.aspect (separate artifact)
 ** tests
 
 * container
 ** 4 diff projects
 ** tests
 *** P1 - org.jboss.classloading
 **** SPI only
 *** P2 - org.jboss.metadata
 **** org.jboss.repository (this one can be dropped; a single interface exists)
 **** SPI
 **** impl: annotation, generic, plugins
 *** P3
 **** org.jboss.annotation
 ***** no SPI
 **** org.jboss.beans.info
 ***** SPI
 ***** plugins
 **** org.jboss.classadaptor
 ***** SPI
 ***** plugins
 **** org.jboss.config
 ***** SPI
 ***** plugins
 **** org.jboss.joinpoint
 ***** SPI
 ***** plugins
 **** org.jboss.reflect
 ***** SPI
 ***** plugins
 *** P4
 **** org.jboss.javabean
 ***** no SPI
 *** (P5) - org.jboss.net, org.jboss.virtual (already moved to VFS project) //
 
 * dependency (org.jboss.dependency)
 ** SPI
 ** plugins
 ** tests

 * deployers (org.jboss.deployers)
 ** SPI
 ** plugins
 ** tests
 
 * kernel
 ** org.jboss.beans.metadata
 *** SPI
 *** plugins
 ** org.jboss.kernel
 *** SPI + Kernel, KernelFactory, KernelPermission
 *** plugins
 ** org.jboss.test.kernel.junit
 *** TODO - where to put this?
 ** tests
 
 * managed (org.jboss.managed)
 ** API (why not SPI?)
 ** plugins
 ** tests
 
 * metatype
 ** API (why not SPI?)
 *** we could separate API into SPI and plugins?
 ** no plugins / impl
 ** tests
 
 * spring-int
 ** no SPI
 ** impl (+ resources/schema)
 ** tests
 
Don't know what you need to do about Eclipse projects.

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

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