Different versions of the same dependency in Maven

java dependencies maven conflict
biziclop picture biziclop · Jan 28, 2011 · Viewed 13.1k times · Source

I have a maven project that depends on both Woodstox and XStream. Unfortunately XStream also depends on Woodstox, but a version slightly older than what I need. In the meantime though, the artifact names of the Woodstox libs changed, so maven won't consider them multiple versions of the same artifact. But the package and class names are the same, which means there is a conflict at runtime.

Now, I could obviously hack the old woodstox jar out of the build (a war file in our case) somehow but what is the proper way of solving this type of problem?

Answer

Raghuram picture Raghuram · Jan 28, 2011

You could try excluding woodstox dependency in your dependency declaration for xstream. 

  <dependency>
        <groupId>xstream.group</groupId>
        <artifactId>xstream</artifactId>
        <version>a.b.c</version>
        <exclusions>
            <exclusion>
                <groupId>woodstox.group</groupId>
                <artifactId>woodstox</artifactId>
            </exclusion>
        </exclusions>
  </dependency>

Related questions

Conflicting library version in a java maven project

When building a maven project that has many dependencies, some of those dependencies depend on the same library but use a different version which is causing errors when running an application. For example, if I add two different project dependencies, …

Read More
How to add local jar files to a Maven project?

How do I add local jar files (not yet part of the Maven repository) directly in my project's library sources?

Read More
How do I tell Maven to use the latest version of a dependency?

In Maven, dependencies are usually set up like this: <dependency> <groupId>wonderful-inc</groupId> <artifactId>dream-library</artifactId> <version>1.2.3</version> </dependency> Now, if you are working …

Read More