Details
-
Enhancement
-
Resolution: Fixed
-
P2
-
9
-
b30
-
Verified
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8085000 | emb-9 | Naoto Sato | P2 | Resolved | Fixed | team |
Description
The current mechanism to determine the available locale providers depends on the JDK layout, specifically it checks if localedata.jar and cldrdata.jar are present.
In JDK 9, localedata and cldrdata will be modules and there will be no localedata.jar and cldrdata.jar.
One option to consider is the use of ServiceLoader to load the CLDR and LocaleData providers.
In JDK 9, localedata and cldrdata will be modules and there will be no localedata.jar and cldrdata.jar.
One option to consider is the use of ServiceLoader to load the CLDR and LocaleData providers.
Attachments
Issue Links
- backported by
-
JDK-8085000 Re-examine the mechanism to determine available localedata and cldrdata
-
- Resolved
-
- relates to
-
JDK-8151479 Performance degradation in JDK 9 b30
-
- Resolved
-
-
JDK-8057646 ClassCircularityError running SQE test
-
- Closed
-
-
JDK-8048588 Granularity of localedata and cldrdata
-
- Resolved
-
-
JDK-8057075 Improve ability to diagnose JRE and CLDR locale provider adapter on resource bundle loading error
-
- Open
-
-
JDK-8058509 CLDRLocaleDataMetaInfo should be in jdk.localedata
-
- Closed
-
(1 relates to)