"scott.stark(a)jboss.org" wrote : I don't follow why. Sure, both product releases would require separate runs of the top level aggregation entry point, but if both were mavenized, projects properly separated, running the top level jbossas release pom target should be able to build everything. The jbossas aggregate doesn't know how to build ejb3 artifacts, only the ejb3 aggregate knows this. So if you run mvn release on jbossas it would complain about ejb3 snapshots. Likewise if you run mvn release on ejb3 it would complain about jbossas snapshots. "scott.stark(a)jboss.org" wrote : In practice I think we should separate the release project from the base artifacts and one would have to run the build in stages. Is that what you mean? | Yes, first you do a mvn release of the jbossas-base, then mvn release ejb3, then mvn release jbossas-product. (In the same sense that we do a mvn release of jboss-metadata, jboss-container & others before we can do the above.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128064#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...