ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "JWM" <>
Subject RE: FTP "Depends" option for size as well as date?
Date Wed, 20 Dec 2006 23:35:20 GMT
I lost you.  Are you saying that if I change the timestamp locally, it will
re-upload?  I don't understand where the hash comes into play.  If I change
the date, it's going to upload anyway.  Does <modified> somehow compare MD5
hash of the file on the server to the MD5 hash of the file locally?  If that
is the case and the upload breaks, shouldn't it catch it as a non-equal hash
the next time I run the ant script?

The problem is that it takes up to 6 hours to upload everything for a single
project.  I only want to upload what needs to be uploaded.  I could do a
"touch" of all the files locally and force upload of everything to guarantee
that all the files are valid.  But re-uploading 6 hours each time is just
not practical when perhaps 95% of the files are still good.

I'm a java programmer.  I'm willing to modify the ftp task to meet my needs
if it's not a huge task.  I just don't have the bandwidth to dive into a
major undertaking, though.  How easy would it be to modify the ftp task


-----Original Message-----
From: [] 
Sent: Wednesday, December 20, 2006 10:11 AM
Subject: AW: FTP "Depends" option for size as well as date?

The <modified> catches all files which were already selected my 
storing their MD5-hash (other algorithms could be plugged in).
So that could help if you change the timestamp locally.

It does not help if your upload breaks.


>-----Urspr√ľngliche Nachricht-----
>Von: JWM [] 
>Gesendet: Mittwoch, 20. Dezember 2006 17:05
>An: 'Ant Users List'
>Betreff: FTP "Depends" option for size as well as date?
>I use the FTP task extensively with the 'depends' option to 
>keep all of the files on my server in sync with my local copy. 
> The problem is that I tranfer many huge files (audio/video) 
>and periodically, an FTP will die in the middle of a transfer.  
>The problem is that even if only two bytes of 100M file got 
>transferred, the target file gets the current date.  The next 
>time I do a transfer, that file is 'current', at least 
>according to the date, and will never be re-uploaded.
>Is there any type of ftp ant task that will also compare sizes 
>of the file as well as time/date stamp to determine if the 
>file needs to be transferred?
>To unsubscribe, e-mail: For 
>additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message