This message was deleted.

I guess you could use an artifact transform for that.

I already did that (figured it out myself)... now I have an issue where I need to also affect the classpath entry order and I can't

The order is the order in which you declare the dependencies. But actually imho if you depend on classpath order that is a smell.

It's not me, it's the environment around me and yes it is awful. Stems from the fact that multiple versions of the same dependency are shaded into multiple other dependencies. I solved it by using artifact transform to remove an old version of that dependency from one of the jar. And the order in the IDE somehow wasn't the declaration order, it was sorted alphabetically by absolute jar path

Yeah, one of the many reasons fat jars are a bad idea, especially if not relocated, especially in libraries.