"scott.stark(a)jboss.org" wrote : But the problem is that there is a chicken & egg problem. jbossas-5.0.0.GA needs ejb3 2.1.x, which needs jbossas-5.0.0.GA SPI jars. If both were mavenized, the dependencies would handle this by having access to all projects during the build. Since jbossas is not mavenized, we have to build the spi artifacts, uploaded to a maven repo, build the ejb3 artifacts, upload to a maven repo, build the ejb3 dependent artifacts of jbossas, build the jbossas assembly product. Its getting this procedure defined/automated that I'm wanting to get defined for jbossas-5.0.0.CR1. | Even if both were mavenized it still wouldn't work, because jbossas and ejb3 run with different aggregators. It needs to become and will from point on always be a multi-stage rocket. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128006#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...