Search code examples
javadependenciesmavenconflict

Different versions of the same dependency in Maven


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?


Solution

  • 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>