"adrian(a)jboss.org" wrote : 4) Longer term EJB3 wants to go its own way anyway so shared dependencies aren't even the correct solution. Yes, but in the interim, EJB3 requires the AS runtime and component-matrix was built to ensure that our compile/runtime dependencies would match. "adrian(a)jboss.org" wrote : 5) The correct way to integrate things is via interfaces NOT implementations. | | In my view EJB3 is just being lazy (can't be bothered creating a version | of EJB3 that isn't so brittle to thirdparty implementation details and versions) | and forcing JBossAS to jump through hoops because of that. You assume that we have access to the SPI/API/interfaces required for us to build. At the moment, the "integration" project (http://anonsvn.jboss.org/repos/jbossas/projects/integration/trunk/) holds SPIs for a whopping 3 projects. Until all of our AS Component dependencies are properly extracted into SPI/Impl, we'll depend on implementations and hence have a cyclic dependency preventing release. The EJB3 team's efforts towards Mavenization has lead to the discovery of cyclic dependencies in AS. The problems were already there, and the new build tool is bringing them to the surface. For this laziness, you are welcome. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140261#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...