Eclipse wouldn't load with b118

[Alan Bateman]

On 18/05/2016 14:42, Jayaprakash Arthanareeswaran wrote:
>
> Hello everyone,
>
> People reported that they are not able to run Eclipse with the latest JDK
> build (b118). This is critical for us and would like to see it resolved as
> soon as possible. We believe this is caused by change in resolution of EE
> modules and further discussion can be found here -
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=493761
>
> One of the work around discussed is adding the following to our launch
> configuration:
>
> -addmods
> java.se.ee
>
> But looks like there might be issues in using this work around. Are there
> other alternatives we could use?
>
The change you see in jdk-9+118 is expected and is a consequence of 
aligning the policy for root modules to that described in JEP 261 [1]. 
See also a note to jdk9-dev [2] about this.

The workaround is `-addmods java.se.ee` as noted in the bug. In this 
case then `-addmods java.annotations.common` might be enough, it depends 
on whether you use other EE modules or not.

So is Eclipse creating the VM with the JNI invocation API? I can't quite 
tell from the issue. At this time then `-addmods` is a java launcher 
option but we are looking to push this into VM so that it can be used by 
custom launchers. This gives you control on whether the option is to be 
ignored when launching older JDKs that don't know about this option.

-Alan

[1] http://openjdk.java.net/jeps/261
[2] http://mail.openjdk.java.net/pipermail/jdk9-dev/2016-May/004309.html