These are good ideas, but I think you're solving the problem in the
wrong place. In the example Bruce posted, the problem was in the ZIP
"file-system" rather than FAT. A single-property solution wouldn't
help there -- it would solve the 2sec granularity for ZIP at the
expense of reduced granulari
my example and that while
it may be unusual, degree of "unusualness" should not be an relevant
metric here. And we can certainly come up with more usual examples, if
you like.
Bruce Atherton wrote:
>Xxx Yyy wrote:
>
>>Thanks for your consideration. I think you are testing
the build-file, or some such). I see the
need for granularity, but, with all due respect, I disagree with how it
was implemented. The change broke my builds and has introduced extra
complexity and a lack of confidence in ANTs disk-based operations.
--- Steve Loughran <[EMAIL PROTECTED]>
I looked, but didn't find any discussion on the new granularity
FileUtils.getFileTimestampGranularity. This is messing up my builds
big-time.
If you are on Windows and you run two COPY operations within two
seconds of each other, the second COPY will be skipped.
