Is there a handy way to either: 1. Materialize a ...
# general
a
Is there a handy way to either: 1. Materialize a
resources
target into a directory 2. Make a zip file of a
resources
target ?
a
this isn't answering the question at all but i would recommend making use of the
deployable_archives
product if there is a task created to do (2)
a
I was hoping not to write any code 😞 I can make an empty
jvm_binary
which depends on it, which will give me a zip file…
a
now that's called being a hacker
w
@average-vr-56795: could extract the
Snapshot
of the resources ?
extract/checkout
a
Does that mean… “Add a flag to filedeps”? 😄
a
if
./pants bundle <target>
doesn't do this for resources it might be very reasonable to add that capability?
w
mm, so you mean "outside of pants" then
a
Yeah, I was hoping to be able to just run
./pants bundle <target>
or similar… The
jvm_binary
hack is sufficient for my needs, though 🙂
a
are there any tasks which consume bare
resources()
targets right now (like as target roots)? or are they only consumed as dependencies of other targets?
the answer is no
i spent 5 minutes thinking about how to make a task for `./pants bundle`ing any
Files
subclasses passed as target roots so if that's a need for anyone let me know, but just stashed it for now