[9] RFR: 8058509: CLDRLocaleDataMetaInfo should be in jdk.localedata

[Mandy Chung]

On 9/16/14 9:57 AM, Naoto Sato wrote:
> Yes, the current plan is to make the CLDR's data the default one, only 
> when it is available. Requiring it in the java.base would be 
> problematic for smaller environments. This will be addressed in 8008577.

Do you mean the EN cldr data is big?

Mandy

>
> Naoto
>
> On 9/16/14, 9:50 AM, Mandy Chung wrote:
>> At one point you mention that CLDR will become the default in JDK 9.
>> Would you need to move them back to java.base when it becomes the 
>> default?
>>
>> Mandy
>>
>> On 9/16/14 9:30 AM, Naoto Sato wrote:
>>> CLDR's data is accessible only when cldrdata.jar is available,
>>> including their "en" resources. There is no need to put their "en"
>>> resources in java.base.
>>>
>>> Naoto
>>>
>>> On 9/15/14, 6:11 PM, Mandy Chung wrote:
>>>>
>>>> On 9/15/2014 4:30 PM, Naoto Sato wrote:
>>>>> Hello,
>>>>>
>>>>> Please review the fix for the following issue:
>>>>>
>>>>> https://bugs.openjdk.java.net/browse/JDK-8058509
>>>>>
>>>>> The webrev is located at:
>>>>>
>>>>> http://cr.openjdk.java.net/~naoto/8058509/webrev.0/
>>>>>
>>>>> The fix is intended to move the LocaleDataMetaInfo of CLDR from
>>>>> java.base module to jdk.localedata module, along with CLDR's "en"
>>>>> locale data and the package name change to avoid the "split package"
>>>>> in two modules.
>>>>
>>>> Should CLDR's en locale data be available when cldrdata.jar is not
>>>> present?
>>>>
>>>> Mandy
>>>>
>>