Eclipse does not yet reliably support JDK9 based development. As such, the mx based Eclipse project configuration mechanism in JVMCI relies on a jvmci.jar to expose JVMCI to a compiler written on top of JVMCI. Currently, this jar file dependency needs to be manually updated for every JVMCI API change.
A better way to fulfill this dependency is for a JVMCI compiler to automatically synthesize jvmci.jar from a JDK9 binary so that the JVMCI API it compiles against exactly matches the JVMCI API available at runtime. Graal now does this[1]. This means the mx build system in JVMCI itself no longer needs to build jvmci.jar.
This issue tracks the removal of building jvmci.jar from the JVMCI mx build system.
[1] http://hg.openjdk.java.net/graal/graal-compiler/rev/77feea4fe00c
A better way to fulfill this dependency is for a JVMCI compiler to automatically synthesize jvmci.jar from a JDK9 binary so that the JVMCI API it compiles against exactly matches the JVMCI API available at runtime. Graal now does this[1]. This means the mx build system in JVMCI itself no longer needs to build jvmci.jar.
This issue tracks the removal of building jvmci.jar from the JVMCI mx build system.
[1] http://hg.openjdk.java.net/graal/graal-compiler/rev/77feea4fe00c