You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Tim Ellison (JIRA)" <ji...@apache.org> on 2007/11/26 18:35:44 UTC
[jira] Commented: (HARMONY-5195) [classlib][luni]
java.util.Calendar doesn't recalculate fields after timeZone changing.
[ https://issues.apache.org/jira/browse/HARMONY-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545522 ]
Tim Ellison commented on HARMONY-5195:
--------------------------------------
Sergey,
The regression test does not work for me (different timezone?)
expected:<[11:35]:16> but was:<[3:34]:16>
junit.framework.ComparisonFailure: expected:<[11:35]:16> but was:<[3:34]:16>
at tests.api.java.util.GregorianCalendarTest.test_ConstructorLjava_util_TimeZone(GregorianCalendarTest.java:153)
at java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:25)
> [classlib][luni] java.util.Calendar doesn't recalculate fields after timeZone changing.
> ---------------------------------------------------------------------------------------
>
> Key: HARMONY-5195
> URL: https://issues.apache.org/jira/browse/HARMONY-5195
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Reporter: Sergey Kuksenko
> Assignee: Tim Ellison
> Priority: Minor
> Attachments: calendar.patch, Greg_calendar_test.patch
>
>
> java.util.Calendar doesn't recalculate fields after timeZone changing.
> For example:
> Calendar c1 = new GregorianCalendar(1999, Calendar.JUNE, 2, 15, 34, 16);
> c1.setTimeZone(new SimpleTimeZone(60000, "ONE MINUTE"));
> String res = c1.get(Calendar.HOUR)+":"+c1.get(Calendar.MINUTE)+":"+c1.get(Calendar.SECOND);
> After that Harmony returns "3:34:16" instead of "11:35:16" as RI does.
> Patch for unit teste for regression testing is done.
> Patch for the issue is done (also the patch slightly improve performance when calendar already parsed time).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.