In order to make the IDE experience more pleasant now that JEP 243 is integrated we would like to use mx (https://bitbucket.org/allr/mx) for IDE configuration generation. For this we have to integrate a few mx support files into the hotspot repository.

The mx support files will be under a dot-directory:

$ hg st --all .mx.jvmci/
C .mx.jvmci/.project
C .mx.jvmci/.pydevproject
C .mx.jvmci/eclipse-settings/org.eclipse.jdt.core.prefs
C .mx.jvmci/hotspot/templates/eclipse/cproject
C .mx.jvmci/hotspot/templates/eclipse/settings/org.eclipse.cdt.core.prefs
C .mx.jvmci/hotspot/templates/eclipse/settings/org.eclipse.cdt.ui.prefs
C .mx.jvmci/hotspot/templates/eclipse/settings/org.eclipse.core.runtime.prefs
C .mx.jvmci/mx_jvmci.py
C .mx.jvmci/suite.py

mx itself is and will stay an external tool. Some documentation on how to use it can be found here:

https://wiki.openjdk.java.net/display/Graal/Instructions
https://wiki.openjdk.java.net/display/Graal/Eclipse

It basically boils down to:

$ mx ideinit

and importing the configuration into your favorite IDE.

This would give every developer the same view of the source code and we can also enforce code-style guidelines.