"scott.stark(a)jboss.org" wrote : So there is a circular dependencies between mc and aop at least in terms of how the mc is now setup as an assembly type of project. If I try to release jboss-container, it depends on the parent jboss-microcontainer from build/pom.xml and does not have a container/{trunk,tags} structure for an individual release. | | aop depends on jboss-container. I can manually release jboss-container, but how should these projects bet setup so that the mvn release process works for such interdependent projects? | Like I said before. The container project (and the classloader project) shouldn't be in the MC build. They are only there because the MC was initially the major consumer while we developed them. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082044#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...