[jboss-dev-forums] [Design of JBoss Build System] - Move dependency management back into app server svn structur

After spending some time updating dependencies in the component-matrix pom while working on the build-thirdparty conversion, it seems that having the component-matrix as a separate project is somewhat error prone. The main issue is that whenever I make a change in the component matrix I have to make sure that the app server is immediately updated to match, otherwise there are build errors. When the dependency management is part of the app server codebase, this is not an issue because everything gets committed together, and built together. So consider the following scenario where I want to change a groupId or a dependency or add a new dependency. 1. Using separate component-matrix I have to update the component-matrix and install it locally. Then I make the matching changes to the app server poms and install it locally. If it works, I commit and deploy the component-matrix. Then I commit the changes to the app server poms. Now someone checks out the updates to the app server poms. They try to build, but they are missing dependencies because their component-matrix pom in their local repository is out of date (by default maven checks for snapshot updates once per day). 2. Having dependency management in the app server svn structure. In this case I can just make my changes locally, test them, and then commit the changes together. If someone does an svn update it will work fine for them because they are building and installing the component-matrix stuff along with the rest of the app server. So option 2 seems to be significantly simpler and less error prone. Other thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139024#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...