Antoine Levy-Lambert wrote:
Do not worry if you are sure that the current behavior is buggy.
Cheers,
Antoine
Well, I went and logged a bug on the issue thinking that this might
provoke a little more discussion. Unfortunately, bugzilla seems to not
have sent out an email about it, so it will get
> I agree with you. I suppose that with the current code, you can always
> "fudge" the granularities by summing them together as timediffmillis in
> the above code which is a settable parameter.
>
> The case I have in mind is this:
>
> ...
> preservelastmodified="true"
> newer=
Martijn Kruithof wrote:
Steve Cohen wrote:
In trying to bring over new commons-net timezone functionaility, I
discover the following:
protected boolean isUpToDate(FTPClient ftp, File localFile,
String remoteFile)
throws IOException, BuildException {
...
Steve Cohen wrote:
In trying to bring over new commons-net timezone functionaility, I
discover the following:
protected boolean isUpToDate(FTPClient ftp, File localFile,
String remoteFile)
throws IOException, BuildException {
...
if (this.action =
In trying to bring over new commons-net timezone functionaility, I
discover the following:
protected boolean isUpToDate(FTPClient ftp, File localFile,
String remoteFile)
throws IOException, BuildException {
...
if (this.action == SEND_FILES) {
