-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
None
-
b06
-
generic
-
generic
Although they are clearly declared "deprecated" in java.util.TimeZone (https://docs.oracle.com/en/java/javase/23/docs/api/java.base/java/util/TimeZone.html#three-letter-time-zone-ids-heading), they still can be used to instantiate TimeZone instance.
one-arg java.time.ZoneId.of() does not support those legacy IDs, but by using `ZoneId.SHORT_IDS` will create ZoneId instances for those IDs.
To eventually get rid of those JDK 1.1 legacy IDs, it is desirable to log/display a warning messagel, if users try to instantiate TimeZone instances with those legacy IDs.
one-arg java.time.ZoneId.of() does not support those legacy IDs, but by using `ZoneId.SHORT_IDS` will create ZoneId instances for those IDs.
To eventually get rid of those JDK 1.1 legacy IDs, it is desirable to log/display a warning messagel, if users try to instantiate TimeZone instances with those legacy IDs.
- causes
-
JDK-8349873 StackOverflowError after JDK-8342550 if -Duser.timezone= is set to a deprecated zone id
-
- Resolved
-
- relates to
-
JDK-8340477 Remove JDK1.1 compatible behavior for "EST", "MST", and "HST" time zones
-
- Resolved
-
-
JDK-8347841 Test fixes that use deprecated time zone IDs
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk/cfe70ebc
-
Review(master) openjdk/jdk/23049