One problem present with EJB3 (and likely other projects in the future) is the lack of a proper dependency matrix. As it currently stands, EJB3 dependencies are defined by the EJB3 Build module, set as the parent POM for the other modules. We are specifying the versions here to match those of AS by hand. If EJB3 is not compiling against the same version that the AS assembly will be placing in the runtime, we're setting ourselves up for disaster with any number of potential version conflicts. There is no contract ensuring that our manual process is valid. All of the proper dependencies are defined in the JBossAS Parent POM. However, EJB3 cannot depend on AS as this introduces a cyclic dependency. Therefore, I'd like to move all of the versioning (dependencyManagement section) of the JBossAS Parent POM to a new project, potentially an AS component. This way, both EJB3 Build and AS Assembly can depend on the same versions/definitions, and we become bound to a shared contract. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136182#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...