Just to clarify, the code that you referenced is in build/build.xml and now also in testsuite/build.xml. The one in build/build.xml generates the properties and filesets that are used to gather all the jars into the distribution. You could certainly parameterize this just by changing <pom file="../thirdparty/pom.xml"/> | To something like: <pom file="${thirdparty.pom}"/> | But changing this wouldn't affect the module builds, so I'm not sure if it would accomplish what you are asking for. If the goal is to build against various versions of dependencies then what would have to change is component-matrix/pom.xml. And there isn't any way that I know of to tell maven to use a different file for that module because the -f option only affects the current directory. I looked into something similar to this a while back (MNG-3150) So when building the whole app server from the root directory, I'm kind of stuck with whatever is in component-matrix/pom.xml. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242941#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...