Resolving transitive dependency conflicts in Java

Question

I am trying to build a Dropwizard (Jersey) REST endpoint that communicates with HBase. Although these are my only two top-level dependencies, both of these dependencies come loaded with many transitive dependencies that conflict. A simple example of such a conflict is Google's Guava:

The HBase client specifies version 11
Dropwizard specifies 18

Dropwizard will not work with version 11 and HBase will not work with version 18.

I have examined the Maven shade plugin documentation, but it does not seem to let you relocate classes found in dependency jars. So I don't know how to resolve this issue short of separating these two components into separate JVMs.

Can you give more details as to why each can't run with an upgraded / downgraded version of guava? — Steve Skrla, Jun 18 '15 at 20:41
The conflicts were a'many, but one that killed me was `com.google.common.base.Stopwatch`, where between versions 17 and 18 the API changed without any form of deprecation — Dmitry Minkovsky, Jun 18 '15 at 20:42
I found this article incredibly helpful https://www.elastic.co/blog/to-shade-or-not-to-shade. Been meaning to post I here for a long time — Dmitry Minkovsky, Mar 25 '17 at 23:38

score 1 · Answer 1 · answered Jun 18 '15 at 20:59

This is a dirty solution. But you could...

Create a project / module where you define a set of service interfaces that your dropwizard app will use to talk to HBase.

Create another module / project that implements these interfaces and uses the HBase classes. Shade this project.

In your Dropwizard project include only the interface jar but create a task to copy the shaded artifact into your resources.

Create a JARClassLoader for your shaded HBase client artifact. You may have to make a special subclass that does not delegate to the parent as by default the classloader will ask the parent to resolve linkages and may pull the newer version of guava from outer classloader.

Ask for an instance of the service contract from the Jar loader...

Businessing api = Class.forName("com.awesome.Businessing", true, jarLoader).newInstance();

score 0 · Answer 2 · answered Jun 19 '15 at 05:41

0

Try to specify concrete versions for those dependencies in <dependencyManagement/> section of you pom.xml.

answered Jun 19 '15 at 05:41

Andrey

513
5
9

Resolving transitive dependency conflicts in Java

2 Answers2

Linked