On Tue, 8 Oct 2024 17:46:16 GMT, Naoto Sato wrote:
> This is indeed surprising that this has not been revealed by now. I guess
> nobody used this old mapping before... Anyway, I am now trying to get rid of
> this old mapping behavior altogether
> (https://bugs.openjdk.org/browse/JDK-8340477),
On Thu, 3 Oct 2024 19:46:48 GMT, Justin Lu wrote:
> Please review this PR which fixes an unexpected exception for
> `TimeZone.toZoneId("HST")` when the old mapping system property is used.
>
> The culprit is in `TimeZone.toZoneId0()`.
>
> This method provides workarounds for "EST", "MST", and
Please review this PR which fixes an unexpected exception for
`TimeZone.toZoneId("HST")` when the old mapping system property 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
