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
I have a custom ShadowJar task and I'm using from() method to add additional jar files. Up to beta8 the added jar files were extracted and that's what I need. But with beta9 they are not - they are just added as *.jar files to my shadow jar.
I have found some inconsistent comments about the from method usage. According to this: https://github.com/GradleUp/shadow/blob/main/src/docs/configuration/README.md#adding-extra-files
the content should be extracted. But according to this PR #1250 it should not. So I'm not sure if the change was intentional? If the answer is yes, how can I achieve the old behaviour?
Related environent and versions
No response
Reproduction steps
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
from means copying the file into the destination in the shadowed jar without unzipping, this is the correct behavior, which aligns with the behavior in Gradle's Jar task. The behavior before 9.0.0-beta9 is wrong...
If you still want to add extracted jars into the shadowed jar, please try out
Expected and Results
I have a custom
ShadowJar
task and I'm usingfrom()
method to add additional jar files. Up tobeta8
the added jar files were extracted and that's what I need. But with beta9 they are not - they are just added as*.jar
files to my shadow jar.I have found some inconsistent comments about the
from
method usage. According to this:https://github.com/GradleUp/shadow/blob/main/src/docs/configuration/README.md#adding-extra-files
the content should be extracted. But according to this PR #1250 it should not. So I'm not sure if the change was intentional? If the answer is yes, how can I achieve the old behaviour?
Related environent and versions
No response
Reproduction steps
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: