JDK-8058509 : CLDRLocaleDataMetaInfo should be in jdk.localedata
- Type: Bug
- Component: core-libs
- Sub-Component: java.util:i18n
- Affected Version: 9
- Priority: P3
- Status: Closed
- Resolution: Fixed
- Submitted: 2014-09-15
- Updated: 2016-06-13
- Resolved: 2014-09-17
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 9 |
|---|
9 b32Fixed  |
Related Reports
|
Relates :
|
Description
CLDRLocaleDataMetaInfo is an implementation of LocaleDataMetaInfo SPI, which provides the information about locales it supports. Currently it resides in java.base module but really it should be in jdk.localedata module, with a different package name from sun.util.cldr (otherwise it would cause a split package both in java.base (sun.util.cldr.CLDRLocaleProviderAdapter) and jdk.localedata. sun.util.resources.cldr.provider is a possible alternative.