Sorry about that.Its not a complaint I did not know how to figure that one out I do know the issue seems to be that there is a jar conflict with xerces and apache commons configuration uses a version that conflicts with the latest which is used by other projects so I added my dependency explicitly to the super pom and now its part of the classpath.and compiles fine when I do a mvn clean install but the thing is when I import it into idea mvn idea:idea i can see the xerces 2.8.1 but becuaes commons-configuration comes first it still seems to be using the xerces with that.. and messing my testcases up I think it uses it alphabetically is there some way i can tell maven explicitly to use the newer xerces in its classpath before the older one..... Cheers Priya -- View this message in context: http://www.nabble.com/weird-maven-behaviour-tf4531828s177.html#a12933996 Sent from the Maven - Users mailing list archive at Nabble.com.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
