I am not sure whether this is a bug, but I noticed an inconsistency between the output of the bootJar task in gradle and the equivalent maven artifact.
I have a gradle project that includes two dependencies with the same name (client-1.0.jar
): the gradle plugin puts them in the same location in the jar file (BOOT-INF/lib
) and when I try to run the jar file I get a NoClassDefFound
exception. If I build the same project with maven it works.
The maven plugin looks for duplicated dependency names, and renames them if necessary (See here).
Would it be possible to do the same in the gradle plugin?
Comment From: bclozel
Closing as a duplicate of #16241