-
Bug
-
Resolution: Fixed
-
P4
-
None
-
b21
-
generic
-
generic
The 3-letter time zone IDs, "EST", "MST", and "HST" were aliased to "America/New_York", "America/Denver", and "Pacific/Honolulu" respectively in JDK1.1. With the introduction of TZdata 2004r, these mappings were removed and they are defined as fixed time zones, such as "EST" as "-05:00." There is an internal system property "sun.timezone.ids.oldmapping" to flip the mappings to JDK1.1 compatible ones.
With the release of TZdata 2024b, those fixed offset mappings are again changed to links to other time zones. Thus the flip switch will become somewhat moot. Removing those codes that bring JDK1.1 behavior would be desirable.
With the release of TZdata 2024b, those fixed offset mappings are again changed to links to other time zones. Thus the flip switch will become somewhat moot. Removing those codes that bring JDK1.1 behavior would be desirable.
- csr for
-
JDK-8340478 Remove JDK1.1 compatible behavior for "EST", "MST", and "HST" time zones
- Closed
- relates to
-
JDK-8341484 TimeZone.toZoneId() throws exception when using old mapping for "HST"
- Closed
-
JDK-8342550 Deprecate JDK1.1 compatible time zone IDs for removal
- Open
- links to
-
Commit(master) openjdk/jdk/71583222
-
Review(master) openjdk/jdk/21545