-
Bug
-
Resolution: Won't Fix
-
P4
-
24
-
None
-
generic
-
generic
TimeZone.toZoneId() throws exception for "HST" when the old mapping is used.
The culprit is in TimeZone.toZoneId0().
This method provides workarounds for "EST", "MST", and "HST" when the old mapping system property is true. However, it seems that "HST" was added with "America/Honolulu" when it should have been "Pacific/Honolulu".
Reproducer,
Set the system property "sun.timezone.ids.oldmapping" as true.
Then run, TimeZone.getTimeZone("MST").toZoneId()
The culprit is in TimeZone.toZoneId0().
This method provides workarounds for "EST", "MST", and "HST" when the old mapping system property is true. However, it seems that "HST" was added with "America/Honolulu" when it should have been "Pacific/Honolulu".
Reproducer,
Set the system property "sun.timezone.ids.oldmapping" as true.
Then run, TimeZone.getTimeZone("MST").toZoneId()
- relates to
-
JDK-8340477 Remove JDK1.1 compatible behavior for "EST", "MST", and "HST" time zones
- Resolved
- links to
-
Review(master) openjdk/jdk/21332