<AWT Dev> Removing all methods that use the AWT peer types in JDK 9

Phil Race philip.race at oracle.com
Tue Feb 17 02:35:47 UTC 2015


On 2/16/15 2:57 PM, Roman Kennke wrote:
> Hi,
>
> Am 16.02.2015 23:45 schrieb Phil Race <philip.race at oracle.com>:
>> Hi,
>>
>> Regardless of any changes to the methods using peers, in a modular JDK
>> nothing
>> else inside the module java.desktop is accessible to external code anyway.
>>
>> The module system has preventing access to module (JDK) internals
>> by code outside that module as a core goal.
>>
>> So (eg!) if you rely on SunToolkit or SunFontManager for a porting
>> layer, then
>> you are going to have to be part of the desktop module in order to use them,
> So, in order to make Cacio stuff work with JDK 9, it needs to be part of the desktop module, in other words, OpenJDK code base. Sounds like it's time for a Cacio JEP :-)
>

Not necessarily.  I imagine this would be a port of the desktop module 
(to create
your JDK) and ports don't have to be in the core openjdk code base and 
indeed
the bar for that is understandably high.

-phil.



More information about the awt-dev mailing list