This is a hill I would be willing to die on: The majority of issues in a #Maven build happen in combination with #shading. It's the worst, but sadly, sometimes inevitable.

@rotnroll666 What is even the use case for Shading? I always feel that something must have gone wrong before so that you feel it's easiest to resort to that stop-gap. Why not fix the root cause instead?

Follow

@stitzl @rotnroll666 My only use case for shading has always been cli applications so that they can be launched via a simple `java -jar ...`. If the .jar spec allowed for a `lib/` directory containing dependencies (akin to a simplified .ear or .war) I would almost never need to shade dependencies anymore. Yes, I'm aware there are some custom classloaders floating around that do the above but it needs to be built into the platform.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.