How to get Graal SDK packages to work without Maven?

GraalVM

GraalVM is a high-performance embeddable polyglot virtual machine currently supporting a number of programming languages: Java (and JVM languages), JavaScript (including node.js), Ruby, R, Python, and C/C++ and other languages with the LLVM backend.

You can download the pre-built distribution of GraalVM here: https://www.graalvm.org/downloads. Among other things it includes a java runtime, a node runtime, a JavaScript engine called Graal.js, etc.

Graal SDK is the polyglot API allowing GraalVM to work with all the language implementations it can run. This polyglot API is packaged as a jar file: $GRAALVM_HOME/jre/lib/boot/graal-sdk.jar.

Adding that file as an external library to your IDEA project / module, would allow the IDE to find the classes like: org.graalvm.polyglot.Context and org.graalvm.polyglot.Value which are necessary to interop with the languages, including the JavaScript implementation.

If your project is using Maven, you can add a system dependency on that file, and maven will find it on any system where $JAVA_HOME is set to point at a GraalVM distribution.

<dependency>
    <groupId>org.graalvm</groupId>
    <artifactId>graal-sdk</artifactId>
    <version>1.0.0-rc</version>
    <scope>system</scope>
    <systemPath>${java.home}/lib/boot/graal-sdk.jar</systemPath>
</dependency>

Now when you will run the java command from the GraalVM distribution, the necessary files will be added to the classpath automatically. So nothing more is necessary to run something like the following in the IDE:

import org.graalvm.polyglot.*;
public class Main {
    public static void main(String[] args) {
        Context polyglot = Context.create();
        Value array = polyglot.eval("js", "[1,2,42,4]");
        System.out.println(array.getArrayElement(2).asInt());
    }
}

Now this is because GraalVM has the Graal.js JavaScript engine enabled by default.

If you want to run it on a stock JDK you need to add more things to the classpath.

Running Graal.js on a stock JDK**

There's this question on how to run Graal.js on the stock JDK: How to use graaljs ? Is there a place where to get a .jar file/files?. The accepted answer tells in more details where to find the necessary jar files to make it work on Java 8.

In a nutshell you need to add the following jar files to the classpath to make it actually run:

• graal-sdk.jar - GraalVM polyglot API
• truffle-api.jar - API for language implementations.
• graaljs.jar - this is the implementation of GraalVM's JavaScript Engine
• graaljs-scriptengine.jar -- allows to use Graal.js through the Java script engine API.
• graaljs-launcher.jar
• tregex.jar -- regexp library
• truffle-profiler.jar - profiler for Truffle languages implementations
• chromeinspector.jar - debugger integration
• launcher-common.jar

You can find them in the GraalVM distribution that you downloaded, both editions would work fine.

Now without the Graal compiler the performance of the JavaScript engine would not be optimal. As you mentioned yourself JDK 11 comes with a snapshot of the Graal compiler (not GraalVM, which is a full distribution of the GraalVM project including JS engine, LLVM bitcode interpreter, node implementation, JVM, etc). You can enable the Graal compiler by passing --XX:+UnlockExperimentalVMOptions --XX:+UseJVMCICompiler to the java command.

Now running it all on JDK 11 might not work because JDK 11 is sufficiently different from JDK 8 and there could be problems with the module system or things missing (like jax-b), but it also might work. It would work on JDK 8.

IntelliJ is not adding all of the Jars from the Graal SDK to your classpath.

You can add the Jars to your classpath inside IntelliJ by navigating to

File > Project Structure > SDKs > Choose your Graal SDK

Then click the + button at the bottom to add the Jar files. Adding the graal-sdk.jar will fix the problem with finding the org.graalvm package.

This will avoid having to modify your pom.xml file to fix a problem with the IDE.

So I found out the problem. IntelliJ IDEA is so much used to the standard JDK Home structure that it was not loading the the Graal SDK and other apis.

The Maven jar files that got me closer to the result were EXACTLY the same files that were bundled with GraalVM.