Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <4957464.365591285256915896.JavaMail.jira@thor>
Date: Thu, 23 Sep 2010 11:48:35 -0400 (EDT)
From: "Sebb (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Commented: (NET-339) Incorrect parsing of timestamp on
 windows
In-Reply-To: <3126659.339851285154794743.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/NET-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914067#action_12914067 ] 

Sebb commented on NET-339:
--------------------------

Thanks.

I wonder now whether Windows CE should be treated as a different OS from Windows, and reserve the new format for that.

Or have you encountered other ordinary Windows (not CE) FTP servers that return times using the 24hr clock?

> Incorrect parsing of timestamp on windows
> -----------------------------------------
>
>                 Key: NET-339
>                 URL: https://issues.apache.org/jira/browse/NET-339
>             Project: Commons Net
>          Issue Type: Bug
>          Components: FTP
>    Affects Versions: 2.0
>         Environment: Windows
>            Reporter: Bram
>            Priority: Minor
>         Attachments: NET-339_v2.patch
>
>
> Somewhere in the past the timestamp format returned by windows/the windows ftp server changed.
> In the past the timestamp had a format like: '09-21-10 06:00PM'.
> The 'current' format however is: '09-21-10 18:00'.
> In version 1.4 this resulted in no files being displayed because parsing the timestamp fails;
> In version 2 this results in the files being displayed but without the timestamp.
> (This is the result of change 645299)
> The attached patch updates the code so that it detects both the old and the new format of the timestamp.
> A bug that also mentions this, or at least the comments, https://issues.apache.org/jira/browse/NET-50

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.