Well, that's confined to jboss-bootstrap-api-embedded, which is for the Embedded AS. When we say "the bootstrap project itself", what does that really mean? * Generic Bootstrap? (Lifecycle and some config w/ minimal dependencies) * MC Bootstrap (Starts and installs the Kernel) * AS Bootstrap (AS-specific configs and grammar) There isn't presently an "Embedded" project with any code now. groupId org.jboss.embedded at the moment contains a build config, an assembly, and test suites. All other code is shuffled off to other components. The reason for this is because I allowed org.jboss.embedded stuff to depend upon AS itself. Embedded AS Bootstrap doesn't need to depend upon AS for anything. I'm open to an argument that the Embedded Bootstrap belongs under the Embedded groupId. But regardless of where the code lives in SVN or its groupId, we can still do releases of it without affecting the AS. S, ALR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261046#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...