What are you trying to do?
Simplify and reducing time in the packaging process of this plugin.
In the early days of the plugin its dependency nexus-platform-api was an uber-jar (a JAR file with all its dependencies inside) and that was causing conflicts on some projects' classpaths.
Many versions ago, including the one currently used in the plugin (4.0.3-01) it's no longer an uber-jar with all dependencies in it so we could consider no longer applying the shadow plugin and publish this plugin as a regular JAR file.
How could we solve this issue? (Not knowing is okay!)
Stop using the shadow plugin.
In the early days of the plugin its dependency nexus-platform-api was an uber-jar (a JAR file with all its dependencies inside) and that was causing conflicts on some projects' classpaths.
Many versions ago, including the one currently used in the plugin (4.0.3-01) it's no longer an uber-jar with all dependencies in it so we could consider no longer applying the shadow plugin and publish this plugin as a regular JAR file.
cc @bhamail / @DarthHater / @shaikhu