Hi,
 
Currently the Copy task does not cause the build to fail when you try to copy a file that doesn't exist.
 
If people want the build to fail when you want to delete a file that doesn't exist then I'm pretty sure they want a build to fail (when failonerror = true) when you want to copy a file that doesn't exist or am I seeing ghosts here ?
 
Any objections to changing this behaviour ?  When failonerror is false, the build should continue ofcourse (but a warning should be logged).
 
If everyone agrees, I'll post a patch tomorrow.
 
Thanks,
 
Gert

Reply via email to