JBossWS supports AS 5.0.0, 5.0.1, Branch_5_x and trunk (version numbers will change in the future). Each AS has it's dependencies specifed using maven. Each of these dependencies specified in AS components matrix has its own dependencies on another subprojects. To be absolutely clear the main problem I'm talking here is: Because we're supporting multiple AS versions we can't construct proper client classpath using maven dependencies.. Example: JBossWS 3.0.5 AS 5.0.0 Q1) Which jaxb-impl version will be used in testing if we don't exclude it? (dependency:tree output from testsuite module in jboss500 configuration) [INFO] org.jboss.ws.native:jbossws-native-testsuite:pom:3.0.5.GA [INFO] +- org.jboss.ws.native:jbossws-native-client:jar:3.0.5.GA:compile [INFO] | +- org.jboss.ws.native:jbossws-native-core:jar:3.0.5.GA:compile [INFO] | | +- com.sun.xml.bind:jaxb-impl:jar:2.1.6:compile ... [INFO] +- org.jboss.ws:jbossws-jboss500:jar:3.0.5.GA:compile [INFO] | +- org.jboss:jbossxb:jar:2.0.0.GA:compile [INFO] | | +- sun-jaxb:jaxb-api:jar:2.1.4:compile ... We can't exclude jaxb-impl neither from jbossws-native-client (note doesn't matter the different group.id) neither jaxb-impl from jbossws-jboss500 because it's compile dependency (it won't compile without it). We could exclude jaxb-impl either from jbossws-native-client or from jbossws-jboss500 in testsuite.pom xml. But doing so for each conflicting component (there are many such) would be a real maintainability nightmare (especially for moving AS versions even they would be fully mavenized as mentioned in above post) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216131#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...