As I was trying to clenan up the classpaths generated by Maven in my IDE I noticed a number of duplicated dependency JARs (for example stax:stax-api-1.0.1 and javax.xml.stream:stax-api-1.0-2).

I cleaned up a number of POMs and added exclusions to fix these duplicates but I wonder if there's a better way to avoid these problems in the longer term, maybe using the Maven dependencyManagement features?

Anybody has a good idea on how to cleanly exclude a JAR or fix its version number in our SCA multi-module project?
--
Jean-Sebastien

Reply via email to