Review request: module graph clean up

[Roger Riggs]

Hi Alan,

Perhaps the desktop module isn't the right place for prefs,
but it does not belong in the base module. The base module
is for essential APIs that all developers need regardless of the
deployment target. For embedded target devices, the preferences
API has no use and is just dead-code, even if it is small.
The base module is IMHO already too large and includes APIs
not needed for all target devices and is over budget.

Roger

On 11/09/2011 10:47 AM, Alan Bateman wrote:
> On 09/11/2011 15:21, mark.reinhold at oracle.com wrote:
>> :
>> On second thought, what's the motivation for this item?  The
>> java.util.prefs package is pretty small.  Why split it out?
>>
>> Its implementation includes some native code, at least on
>> Posix and Windows.  Are we going to move that to a separate
>> shared library as well?
>>
>> - Mark
> I have to own up here and say that I mentioned to Mandy recently that 
> I didn't think that the desktop module was the right place for the 
> preferences API. I don't think it's an API that even got too much 
> traction but I think should be usable in contexts where the desktop 
> module is not installed. It is small and a good candidate for 
> aggregation. The native methods are currently in libjava, so in the 
> base module.
>
> -Alan.