You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Richard Liang (JIRA)" <ji...@apache.org> on 2007/02/08 10:00:29 UTC

[jira] Resolved: (HARMONY-3004) [classlib][luni]GregorianCalendar.getActualMaximum(Calendar.DST_OFFSET) always return 0

     [ https://issues.apache.org/jira/browse/HARMONY-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Liang resolved HARMONY-3004.
------------------------------------

    Resolution: Fixed

Hello Tony,

I've fixed the issue at revision r504827 with minor change of your test case. Please verify it's fixed as you expected. Thanks a lot.

Best regards,
Richard

> [classlib][luni]GregorianCalendar.getActualMaximum(Calendar.DST_OFFSET) always return 0
> ---------------------------------------------------------------------------------------
>
>                 Key: HARMONY-3004
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3004
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>            Reporter: Tony Wu
>         Assigned To: Richard Liang
>
> Seems we have not implemented it yet.
> following testcase passes on RI whereas fails on Harmony
>     public void test() {
>         Date date = new Date(Date.parse("Feb 28 00:00:01 GMT 2000"));
>         GregorianCalendar gc = new GregorianCalendar();
>         gc.setGregorianChange(date);
>         gc.setTimeInMillis(Date.parse("Dec 1 00:00:01 GMT 2000"));
>         assertEquals(7200000, gc.getActualMaximum(Calendar.DST_OFFSET));
>     }

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