[jboss-dev-forums] [Design of JBoss Build System] - Re: Updating versions in AOP build

[pgier]

The pom in the thirdparty directory was pointing to the 2.0.0.CR16 version of the aop parent pom in the root directory.  So it was still inheriting the old dependency versions.  I changed it to point to the 2.0.0-SNAPSHOT version of the aop parent (the version currently in the project root directory) and then the thirdparty build works fine.

Whenever we do a release we have to remember to update the versions in all the poms.  Eventually I will automate this, but right now it is manual.  If you want, you can change all the poms to the next release version so you don't have to remember to do this during the release process.  You just won't be able to deploy a snapshot version if the version in the poms is not snapshot.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175319#4175319

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175319