My experience differs from yours, and my experience is backed up by a quick glance at the code and the places where there are tests such as:
if (src.lastModified() > dest.lastModified()) { task.log(files[i]+" added as "+dest.getAbsolutePath()+" is outdated.", Project.MSG_VERBOSE); [in SourceFileScanner.java, and again in FileUtils.java] And personal experiences where I forgot that <copy> was timestamp based and one day got burned when the date of the destination postdated the source (on CD) , and our install failed. If copy really does not work for you, then it may be due to clock differences across a network, or something. As an aside, are you doing this on a DOS, rather than NTFS file system? ----- Original Message ----- From: "Ma, Jian" <[EMAIL PROTECTED]> To: "'Ant Users List'" <[EMAIL PROTECTED]> Sent: Friday, December 07, 2001 6:37 PM Subject: RE: copying on files changed > my experience with copy is that if the destination file exists already, it > doesn't do anything even if you've made changes to the src file(It could be > I didn't set some attribute correctly). I used <dependset> to solve this > problem. You can define dependent relationship between src and target > files. Whenever src files got changed, ant detects it and remove all the > target files to force copy to regenerate them. > > Jian"Chuck" Ma > KMV LLC > 1620 Montgomery St. Suite 140 > San Francisco, CA 94111 > 415-352-1157(w) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>