[module-imports] Importing java.se?

Alex Buckley alex.buckley at oracle.com
Wed Sep 4 19:33:50 UTC 2024


On 7/17/2024 1:38 PM, Alex Buckley wrote:
> On 7/17/2024 1:01 PM, Stephan Herrmann wrote:
>> Where will the update be posted?
> 
> JEP 261 will be updated inline, in a way that distinguishes the original 
> Java 9 rule from the Java 11 rule.

Updated: https://openjdk.org/jeps/261#Root-modules

>> Meanwhile I found this in the announcement on jigsaw-dev:
>>      "As the policy is JDK-specific it means there aren't any 
>> specification changes."
>>
>> How does this match to the existence of a compiler that is not part of 
>> JDK? Should that compiler not implement the change?
> 
> JEP 261 has scope SE, not scope JDK, so it was intended that the default 
> set of root modules is a characteristic of the Java Platform, not just 
> the OpenJDK implementation. We'll need to look into why java.lang.module 
> says the default set of root modules is implementation specific, and why 
> the CSR ended up with scope JDK.

We have filed a bug to address the SE-versus-JDK matter: 
https://bugs.openjdk.org/browse/JDK-8338743

Note that `import module java.se` (or any other aggregator module) will 
still not be possible from code on the class path unless there is a 
*further* change to the definition of the default set of root modules.

Alex


More information about the amber-spec-experts mailing list