You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
shadowJar by default depends on the runtime scope, so all it's dependencies should be included. if you have a reproducible example you can post, I'd be happy to look.
That line resolves the configuration and sets the resulting file paths as an input for the task but in this process it's losing the context of the task dependency that produced that file.
I have a multi-module build with both compile and runtime dependencies on other projects:
I would expect both to end up in the shadow jar when running
gradle shadowJar
, but only the "compile project" ones do.As a workaround,
gradle build shadowJar
will cause both compile and runtime project dependencies to be bundled.The text was updated successfully, but these errors were encountered: