This fixes a regression found while backporting the fix for JDK-8382020.

The previous fix records metazone names only when processing the default (001) 
time zone for the metazone. However, it did not handle the case where that 
default time zone also has its own zone-specific names.

This does not show up in mainline for `Hawaii_Aleutian` metazone, because the 
metazone's default time zone is `America/Adak`, which maps back to the 
`Hawaii_Aleutian` metazone. In JDK 25, however, the default time zone for 
`Hawaii_Aleutian` is `Pacific/Honolulu`, which has its own zone-specific names 
so that Hawaii can use short names such as `HST`/`HDT` instead of `HAST`/`HADT`.

As a result, when the JDK-8382020 fix is backported to JDK 25, the 
`Hawaii_Aleutian` metazone names are not generated during the build. This 
change processes metazone names before zone-specific names, so the default-zone 
metazone entry is still recorded even when the default zone has its own names.

---------
- [x] I confirm that I make this contribution in accordance with the [OpenJDK 
Interim AI Policy](https://openjdk.org/legal/ai).

-------------

Commit messages:
 - initial commit

Changes: https://git.openjdk.org/jdk/pull/31046/files
  Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=31046&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8383825
  Stats: 42 lines in 1 file changed: 22 ins; 16 del; 4 mod
  Patch: https://git.openjdk.org/jdk/pull/31046.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/31046/head:pull/31046

PR: https://git.openjdk.org/jdk/pull/31046

Reply via email to