[foreign-abi] minimizing the surface of restricted native access

[Ty Young]

On 12/2/19 2:33 AM, Maurizio Cimadamore wrote:
>
> On 01/12/2019 01:54, Ty Young wrote:
>>
>> On 11/30/19 4:45 PM, Maurizio Cimadamore wrote:
>>>
>>> On 30/11/2019 06:34, Ty Young wrote:
>>>> Well, not all JDK developers got or read the memo then. Doing 
>>>> "jdk.internal." for me brings up: 
>>>
>>> Define "brings up" please?
>>
>>
>> What pops up in Netbeans when adding another module to your project's 
>> module-info.java.
>>
>>
>> I'm not sure how they are visible - the module-info.java only exports 
>> to specific internal modules anyway.
>
> Sounds like an issue specific to Netbeans. I'd suggest to try with a 
> plain module-info.java with your favourite editor - then compile it 
> from the command line and see what happens - I'd be surprised if javac 
> actually let you depend on internal modules (jshell for example doesn't).


Found the issue: they are opening the modules at the IDE level and it's 
leaking into projects. I'm guessing they depend on it for various IDE 
functionality.


I'll hit them up on their mailing list and see if they can fix it somehow.


>
> Maurizio
>
>>
>>
>> *Xfiles theme plays*
>>
>>
>>>
>>> Can you find any "jdk.internal' exported packages in here?
>>>
>>> https://download.java.net/java/early_access/jdk14/docs/api/
>>>
>>> (try to type jdk.internal in the search box and see if anything 
>>> comes up).
>>>
>>> Maurizio
>>>