This message was deleted.
# community-support
s
This message was deleted.
j
I assume gradle gets involved because it uses a
Copy
task for some internal use instead of manually performing these file operations
v
Heavily depends on how this is done, yeah. If that plugin for example uses Gradle dependency resolution mechanism to download the file, for example with a Ivy repository, the Gradle dependency cache would cache that downloaded file.
j
I dont think so. Looks like its just from a http url
afaik I expect a hack to just get gradle to stop tracking the file would do but I have no idea how to do it
v
You probably shouldn't. Tasks should properly define their inputs and outputs, so that up-to-date checks and / or task output caching can work properly, and that you can properly wire task outputs to task inputs to automatically get necessary task dependencies implicitly.
As the input of that task is a remote URL, the task is probably always out-of-date though and that rightous, as you can never know whether the external URL changed. So it is most probably just correct, that the task is rerun and the stale output file is deleted. Even if the stale output file is not deleted, I'd guess the task would re-download the file. But as I said, heavily depends on the concrete details of that task.
j
Yeah. I might need to take a bit closer look at the task