"scott.stark(a)jboss.org" wrote : It still was not building for me: | | | | [starksm@succubus common-core]$ mvn release:prepare -DdryRun=true | | etc... | | | | until I updated my local repository maven2/jboss/jboss-common location to pull in the new parent pom. | Sorry about that, I guess when it looked in the relative path, it only found the new snapshot version. And the common-core pom didn't have the jboss repository listed, so it didn't know to get it from there. I changed the common projects so that they now extend directly from the jboss-parent. And they now have the appropriate repository configuration so that they can find the parent. The common projects will also be getting a group ID of "org.jboss" now instead of just "jboss". This will follow the maven conventions a little better, and allow us to differentiate open source projects vs. commercial projects (com.jboss) in the future if we want to. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053581#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...