Keeping ejb3 in the jbossas project really does not solve anything as far as I can see. Its using a different build system that has to be integrated through either maven repos, jbossbuild repos, or module classpaths. Having it out allows for the developers to do work without breaking the as build. Until they produce an artifact its not impacting jbossas. The problem of as not having proper spis for the ejb3 dependencies needs to be solved regardless. ejb3 does have a proper dependency graph now. If what it depends on it does not have an spi, then that jbossas project needs to be broken up. We already have an integration project. If we want to make it a requirement that all ejb3 dependencies are coming from there, fine. I'll post what the ejb3 project dependencies coming from the jbossas project are today. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131953#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...