"pgier" wrote : Just to clarify, the code that you referenced is in build/build.xml and now also in testsuite/build.xml. | Correct. "pgier" wrote : | 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}"/> | | | That would be helpful. "pgier" wrote : | But changing this wouldn't affect the module builds, so I'm not sure if it would accomplish what you are asking for. | Right. But i will be ensuring that i will use the same overriden pom file during the module builds too. anonymous wrote : | 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) That's interesting. Infact i was going to try using the -f option for multi-module project. The usecase that i am working on involves a custom plugin which will trigger the Maven build for a given project. So if the thirdparty pom file name could be configurable then i could use that param through my plugin to trigger the build. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242947#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...