[
https://issues.apache.org/jira/browse/NET-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502143
]
Rory Winston commented on NET-159:
----------------------------------
Hi Julien
1. We cant make the assumption that remote timestamps will be GMT, they can in
fact be an arbitrary timezone.
2. We may need to tweak the logic, however, I think your example is incorrect
here. Disabling rollback on e.g. 1-Jan-2007 should display all recent format
files correctly. Unless you are talking about files created on, for example,
December 31st, and displayed using a recent file format, in which case, I think
there may be a possibility that these files could be marked with the incorrect
year. So maybe there might be a case for some sort of change along the lines
you have mentioned - maybe something like:
if (remote is recent_date_format and remote.time > now)
if (now.day == remote.day && now.month == remote.month) then dont rollback
else rollback
3. The changes are on the 2.0 branch:
http://svn.apache.org/viewvc/jakarta/commons/proper/net/branches/JDK_1_5_BRANCH/?sortby=date
> FTPFile.getTimestamp() is off by one year
> -----------------------------------------
>
> Key: NET-159
> URL: https://issues.apache.org/jira/browse/NET-159
> Project: Commons Net
> Issue Type: Bug
> Affects Versions: 1.4
> Environment: winxp, jdk 1.5
> Reporter: dangerOp
> Priority: Minor
> Fix For: 2.0
>
>
> The Calendar object returned by FTPFile.getTimestamp seems to be short by one
> year.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
