I’ll explain what an uber JAR is first because this underpins the shading explanation. Uber JAR An uber JAR is a JAR which contains the contents of multiple JARs (or, less commonly, multiple other JARs themselves) Your application will almost certainly use other packages and these packages might be provided as JARs. When using Maven … Read more
You might also have run into a limitation of maven-shader-plugin. It replaces the default jar artifact (created by maven-jar-plugin). This works fine on a clean build, but on a rebuild where the jar is not regenerated, the shader runs again on the jar it created last time, which already contains copies of all the class … Read more
You can add the following configuration so that the contents of the .schema files from all the jars get appended together. <configuration> <transformers> <transformer implementation=”org.apache.maven.plugins.shade.resource.AppendingTransformer”> <resource>META-INF/spring.handlers</resource> </transformer> <transformer implementation=”org.apache.maven.plugins.shade.resource.AppendingTransformer”> <resource>META-INF/spring.schemas</resource> </transformer> </transformers> </configuration>
Uber JAR, in short, is a JAR containing everything. Normally in Maven, we rely on dependency management. An artifact contains only the classes/resources of itself. Maven will be responsible to find out all artifacts (JARs etc) that the project depending on when the project is built. An uber-jar is something that takes all dependencies, and … Read more