I evaluated both 1) current maven dependencies approach 2) and additionalClassPath approach My conclusion: Current 1) approach is better one according to the fact our tests framework is fully mavenized. It's because dependencies classpath specified in modules/testsuite/pom xml is also reused in modules/testsuite/*-tests/pom.xml submodules for invoking JBossWS tools. If we would want to remove current testing approach it would mean to antize it again (step back). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217786#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...