ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacob Kjome <>
Subject <copy> and <move> update timestamp even if overwrite="false"
Date Fri, 30 Jul 2004 20:35:58 GMT

I have noticed that the <copy> and <move> tasks update the file timestamp even
if overwrite="false", making it somewhat hard to determine whether it is only
touching the file or actually ignoring the overwrite="false".  So, I have two

1. What is actually happening, a mere "touch" of the file or an invalid overwrite?
2. If it is only a mere "touch", should this be considered buggy behavior?  Can
the "touch" be avoided?

BTW, why is the "overwrite" default for <copy> "false" while it is "true" for
<move>?  Is that an oversight which now can't be changed to preserve backward
compatibility, or is there a logical reason for the difference?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message