Folks, these dependencies currently prevent the scheduled Beta5 release on 01-Dec-2009 | <version.jboss.classloading>2.0.8-SNAPSHOT</version.jboss.classloading> | <version.jboss.deployers>2.0.9-SNAPSHOT</version.jboss.deployers> | <version.jboss.kernel>2.2.0-SNAPSHOT</version.jboss.kernel> | We proabably need to rollback to the versions that are installed in jboss-6.0.0.M1 otherwise the JBoss OSGi release cannot happen. I realize that framework trunk needs to work with possibly newer SNAPSHOT versions than are installed in the supported target containers. As a consequence we probably need to decouple the MC Framework from JBoss OSGi and move it out of the reactor to projects/runtime/framework/trunk where it originally cam e from. The downside of this is that the framework independent integration tests (i.e. examples, functional) are not available for trunk anymore, which was the original motivation to make framework a reactor project. If framework should stay a reactor project we cannot update the above mentioned dependencies in an uncoordinated way. Compatible updates are ok however as long as the enterprise examples run in all supported target containers. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4267205#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...