RFR: 8206980: DateTimeFormatter throws parsing a valid string depending on the locale
Roger.Riggs at Oracle.com
Wed Jul 11 21:25:06 UTC 2018
On 7/11/2018 1:42 PM, naoto.sato at oracle.com wrote:
> Please review the changes to the following issue:
> The proposed fix is located at:
> CLDR time zone names in "en" bundle are expected to be pre-populated
> for performance. This is not the case for locales that have "en-001"
> (World English) as the parent bundle, such as Locale.CANADA. The fast
> path determining logic was incorrectly assumed all English locales are
> using pre-populated bundles. Limiting the assumption to only "en" and
> "en-US" will solve the problem.
More information about the core-libs-dev