[jboss-dev-forums] [Design of JBoss Build System] - Re: JBossAS CR1 build plan

[dimitris@jboss.org]

I had an interesting discussion with Brian, after the call. He made the very simple observation that until all EJB3 dependencies are identified and externalized (by introducing proper SPIs) what we are having now is a fake independent ejb3 project that complicates thing and doesn't add any real value.

1) Break ejb3 into multiple modules inside the AS codebase (i.e. as per their new ejb3 subprojects). That is, let ejb3 refactor itself into components the way they want.

2) For every other AS module EJB3 depends on, break out the  portion that is API/SPI into a separate project like I did with the cluster module.  Once that's done, ejb3's dependency on that module is gone.

3) Once each module dependency is gone, *then* ejb3 is really independent; that's when you pull the ejb3 modules out of the AS source tree into their own independent project.

Or else, until the dependency graph for EJB3 is properly mavenized, the project should not move outside AS, causing all this trouble and jumping through hoops.

It really boils down to priorities here (AS5 CR1 vs EJB3 externalization) in which case that looks like a sensible plan C to me.

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

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