-
Bug
-
Resolution: Not an Issue
-
P4
-
None
-
1.3.1
-
sparc
-
solaris_8
hercule.li@prc 2001-01-09
java version "1.3.1beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1beta-b13)
Java HotSpot(TM) Client VM (build 1.3.1beta-b13, mixed mode)
java version "1.4.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta-b46)
Java HotSpot(TM) Client VM (build 1.4beta-B45, mixed mode)
We think the date 9/9/1999 should belong to
daylight time in Australia/Sydney .
But the testing result is reversed.
In merlin b46, there is a funny phenomenon. :-)
9/9/2000 belongs to daylight time, but
9/9/1999 and 9/9/2001 don't .
In ladybird b13, 9/9/2000 , 9/9/1999 and 9/9/2001
all don't belong to daylight time .
so there are different behaviors in ladybird and merlin.
It must be a bug.
To reproduce the bug, try attached file
TZ_inDaylightTime_y2k.java
------ hercule.li@prc 2001-01-09
java version "1.3.1beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1beta-b13)
Java HotSpot(TM) Client VM (build 1.3.1beta-b13, mixed mode)
java version "1.4.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta-b46)
Java HotSpot(TM) Client VM (build 1.4beta-B45, mixed mode)
We think the date 9/9/1999 should belong to
daylight time in Australia/Sydney .
But the testing result is reversed.
In merlin b46, there is a funny phenomenon. :-)
9/9/2000 belongs to daylight time, but
9/9/1999 and 9/9/2001 don't .
In ladybird b13, 9/9/2000 , 9/9/1999 and 9/9/2001
all don't belong to daylight time .
so there are different behaviors in ladybird and merlin.
It must be a bug.
To reproduce the bug, try attached file
TZ_inDaylightTime_y2k.java
------ hercule.li@prc 2001-01-09
- relates to
-
JDK-4230123 TimeZones loaded unnecessarily
- Resolved