the other is an input that the uberjar needs - you can create a task or step that deletes the original though

or rewrite the uberjar task so it doesn’t need that jar to be created first?

Not always through. Especially when using java libraries, there might be some logging or other dependencies coming along as dependencies, which you don't need, and can be excluded. And when at runtime you have other dependencies on your classpath, you also don't need them in the uberjar. But if you want to use it to run in docker you want all dependencies.

the all-included uberjar always uses the entirety of the regular jar that doesn’t include deps