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=34941>. 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=34941 Summary: FTP uptodate calculations wrong Product: Ant Version: unspecified Platform: All OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Optional Tasks AssignedTo: dev@ant.apache.org ReportedBy: [EMAIL PROTECTED] Given the following task call <ftp action = "get" ... preservelastmodified="true" newer="true"> <fileset.../> </ftp> If this is executed a second time, all files included in the fileset will be retrieved regardless of whether or not they have changed on the server in the intervening time interval. This is because the underlying uptodate logic is returning false if the source and destination timestamps are equal. Logically, it should be true. Logically, any file where the local file's timestamp is greater than or equal to the remote file's timestamp is up to date. Any file whose local timestamp is less than its remote file's timestamp is not. But that's not the current implementation. A similar issue exists on put. The fix is easy to implement and I will do it, but I want to give the community a chance to comment before implementing. There may be a use case for the existing functionality that I am not understanding, or there may be an important backward compatibility issue that I am missing. -- 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]
