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

           Summary: Granularity of COPY too large on modern Windows
                    platforms
           Product: Ant
           Version: 1.6.2
          Platform: PC
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: major
          Priority: P2
         Component: Core
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


I recently upgraded ANT from 1.5 to 1.6.2.  My builds started failing with 
timing problems because of the recent addition of granularity.  Prior to 
1.6.2, COPY would perform an absolute comparision of timestamps to see if a 
file should be copied.  It now uses a 2second granularity window instead, when 
ANT is run on "DOS"-based systems.  This new 2second window breaks my builds 
under Windows 2000 and Windows Server 2003.

I don't know the history behind this change.  Perhaps the 2 second grace 
period is realistic for old MS-DOS systems.  But it is not realistic in modern 
Windows systems.

Assuming that 2-seconds is reasonable for MS-DOS systems, I propose that the 
ANT family test be refined so that the default for Windows systems (NT and 
beyond, at least) is 0 and a granularity of 2 be limitted to older systems.

Even better, the granularity should always default to 0, and the build.xml 
author should be allowed to override the granularity where it is appropriate 
to the local environment.  This would preserve backwards compatability, remove 
a special case, and be much more understandable in general.

-- 
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]

Reply via email to