I guess I'm not sure how/if this will solve the circular dependency issues. If the new parent lists dependencies on ejb3 for example, that app server depends on, doesn't that mean that ejb3 would have to be released before the new parent? Since you are technically not supposed to release the parent if it still lists dependencies on a SNAPSHOT version of ejb3. The same thing would be true for the app server module versions in the new parent pom. Maybe the app server module and ejb3 dependencies should not be listed in the parent? I guess the other option is to release all three at the same time. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137427#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...