You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Niall Pemberton (JIRA)" <ji...@apache.org> on 2011/01/12 01:48:45 UTC

[jira] Commented: (LANG-593) Testing with JDK 1.7

    [ https://issues.apache.org/jira/browse/LANG-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980472#action_12980472 ] 

Niall Pemberton commented on LANG-593:
--------------------------------------

With b102 the same problem with FastDateFormatTest exists
With b124 the same problem with FastDateFormatTest exists and now ExtendedMessageFormatTest also fails

The problem with ExtendedMessageFormatTest is that it is using Locale.getDefault() when no Locale is supplied, which is returning Locale..en_US - but DateFormat & Number format are now (in b124) using the new Locale.getDefault(Locale.Category.FORMAT) which is returning Locale.en_GB. So this appears to be a bug in the 1.7 JDK

> Testing with JDK 1.7
> --------------------
>
>                 Key: LANG-593
>                 URL: https://issues.apache.org/jira/browse/LANG-593
>             Project: Commons Lang
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.5
>            Reporter: Niall Pemberton
>             Fix For: 3.0
>
>
> I ran the tests for the Lang 2.5 RC2 using JDK 1.7.0-b78 and they all passed except the testFormat() in FastDateFormatTest.
> The problem seems to be that in JDK 1.7 the "yyy" and "y" patterns now cause a four digit year with SimpleDateFormat - whereas previous JDK versions resulted in a 2 digit year (as FastDateFormat does).
> JDK 1.7 hasn't yet been released and that may be fixed in the JDK by the time it is, but I thought it worth making a note.

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