DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33906>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33906 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2005-03-08 17:20 ------- The reason behind this change is that FAT16 and FAT32 filesystems have limited granularity, even when running under WinNT. It is not enough to check the OS, it is a per filesys problem, which means that it is essentially a per-directory feature on a sufficiently distributed filesys. This is why, when changing this stuff, we added a granularity attribute to <copy>; you can select a tighter granularity if need be. Note that even on unix, we have a granularity of 1; I wouldnt go for zero on anything. Millisecond accuracy is what we really need, but no FS goes to that detail. I'm marking as worksforme because of the granularity option. This isn't quite what you want, which is a broad, cross-system granularity switch, but probably the best we can easily do. However, I am thinking about whether we could have a generic ant.filesys.granularity property that sets it for a project. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]