Can someone explain how the up to date checking logic is supposed to work. What
exactly does it do with the task.inputs and task.output settings?
This doesn't seem to work for the current Copy task. I don't understand how the
up to date code can know which input files are important (match the CopySpec)
and what files in the output a particular input file maps to. This seems like
knowledge that only the Copy task has. Because of this, I'm not convinced that
the Copy task should use the up to date checking.
Currently, the Copy task seems broken and it is preventing me from using the
trunk version of Gradle. It will only do a copy the first time. If I delete
files in the target area (for example by doing a clean), it will never copy them
again if the source does not change.
I could not see where the TaskInputs were being set for the Copy task and didn't
know how to disable this for a particular instance.
--
Steve Appling
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
