I'm using artifact 1.1.3 as a dependency, getting some fastutil class conflicts. mvn dependency:tree gives the following snippet:
[INFO] +- org.netpreserve.commons:webarchive-commons:jar:1.1.3:compile
[INFO] | +- org.json:json:jar:20131018:compile
[INFO] | +- commons-httpclient:commons-httpclient:jar:3.1:compile
[INFO] | +- commons-io:commons-io:jar:2.4:compile
[INFO] | +- org.gnu.inet:libidn:jar:1.15:compile
[INFO] | +- it.unimi.dsi:dsiutils:jar:2.0.12:compile
[INFO] | | +- it.unimi.dsi:fastutil:jar:6.5.2:compile
[INFO] | | +- com.martiansoftware:jsap:jar:2.1:compile
[INFO] | | +- commons-configuration:commons-configuration:jar:1.8:compile
[INFO] | | +- commons-collections:commons-collections:jar:3.2.1:compile
[INFO] | | \- org.apache.commons:commons-math3:jar:3.1.1:compile
[INFO] | +- org.apache.httpcomponents:httpcore:jar:4.3:compile
[INFO] | \- fastutil:fastutil:jar:5.0.7:compile
As you can see, we're pulling in both fastutil 5.0.7 and 6.5.2, but since they have different groupIds, mvn doesn't exactly know how to resolve. The two different versions have slightly different APIs, so there's a potential here for nasty bugs.
I'm using artifact 1.1.3 as a dependency, getting some fastutil class conflicts.
mvn dependency:treegives the following snippet:As you can see, we're pulling in both fastutil 5.0.7 and 6.5.2, but since they have different groupIds, mvn doesn't exactly know how to resolve. The two different versions have slightly different APIs, so there's a potential here for nasty bugs.