This message was deleted.
# dependency-management
s
This message was deleted.
1
i
Nevermind, I can just
from(configurations.foo)
👍 1
☝️ 1
v
Also, if you actually need the ZIP contents as files and if you want to get even more fancy, you might eventually use an artifact transform to extract the files instead of a
Sync
task. 🙂
i
I read a bit about those in the docs, but I'm really not sure how to put that into practice. It feels weird to me that they are work that Gradle does, but they're not tasks, do not follow the same input rules, do not have a concept of caching (or it's implemented differently?). I'm struggling to understand when they should be used and how.
v
It's not correct that they do not follow input rules and do not have caching. There is
@CacheableTransform
with which you can annotate a transform so that its work can also be cached like task outputs. Of course for unpacking it is not worth to mark it cacheable just like it also would not be worth be for an according task.
👍 1
The unpacking of the dependency files is actually the example that is used in the documentation. Another use-case is for example to on-the-fly modify jars, like signing the jars, or signing DLLs that are inside jars, or dynamically adding a
module-info.class
or
Automatic-Module-Name
manifest attribute like the
extra-java-module-info
plugin does.