maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Metzger <>
Subject Build behavior differences between 3.2.5 and 3.3.9 with dependency shading
Date Thu, 10 Dec 2015 12:59:48 GMT

The Apache Flink project is using Maven for dependency management. We shade
Google's Guava away (to to
avoid conflicts with user guava versions.

Building Flink with Maven 3.2.5 will create a valid fat-jar without guava.
However, Maven 3.3.9 (and other 3.3.x versions) are including guava in the
com/google/commons namespace.
Interestingly, doing only a "clean install" in the "flink-dist" package
after a build of the parent pom results in a correct "flink-dist" fat jar.

I'm wondering which behavior of Maven is correct 3.2 or 3.3 ?
I have the feeling that 3.3 is behaving incorrectly because the
dependency:tree of "flink-dist" does not contain Guava.
Maybe a "clean install" on the parent pom with Maven 3.3 is not respecting
the dependency-reduced poms created by the other modules?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message