JDK-8048588 : Granularity of localedata and cldrdata
  • Type: Task
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 9
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2014-06-27
  • Updated: 2016-03-23
  • Resolved: 2016-03-23
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.
JDK 9
9 b111Fixed
Related Reports
Relates :  
JDK-8038436 - Re-examine the mechanism to determine available localedata and cldrdata
Relates :  
JDK-8148346 - Reduce number of packages in jdk.localedata module
Sub Tasks
JDK-8164746 :  
Documentation for the granularity of localedata / jlink plugin - Resolved
Description
Re-examine and decide the granularity of localedata and cldrdata modules.

This comment from Alan/Mandy, respectively, should also be considered with this CR:

"One comment on the test Bug8038436 is that it sets java.ext.dirs on the
assumption that the locale and cldr data wouldn't be found. I suspect
this will need to be re-worked once we get to the point of linking
modules into the image. It may be that the ext directory is empty by
default (localdata.jar and cldrdata.jar will not exist). "

"GensrcCLDR.gmk and GensrcLocaleDataMetaInfo.gmk generate sources for
java.base and jdk.localedata.  I think we should re-examine to modify
the tool e.g. to take an input parameter specifying which locales or
module the source is generated for.  This will make the i18 build
better fit the new modular build logic such that Gensrc-java.base.gmk
generates the source for java.base and a new Gensrc-jdk.localedata.gmk
generates the source for jdk.localedata."
Comments
Provided a new plugin for jlink tool to offer an option to include locales from jdk.localedata, in addition to US English.
23-03-2016
In addition to exporing a jlink plugin then we are also mostly in agreement that we should reduce the number of packages (the jdk.localdata module has >900 concealed packages). I have created a sub-task to track this issue.
27-01-2016
One possible approach to explore is a jlink plugin that adds an option to limit the locales, for example limiting by language: jlink --addmods jdk.locatedata --limitlocales zh,ja,ko,vi ... This would filter the resources to only the resources for the given languages and also generate the LocaleDataMetaInfo classes with the catalog of the resources in the module.
11-01-2016
Not much request other than dividing en_US locale in java.base and rest in jdk.localedata. Defering this to JDK10 if we get more requirements.
08-09-2015