◀Table of Contents

Configure Native Image Using Shared Reachability Metadata

With the Gradle plugin for GraalVM Native Image you can easily build a native executable from a Java application. The plugin is provided as part of the Native Build Tools project and uses the Gradle build tool. If the application does not dynamically load any classes at run time, then your workflow is just one command: ./gradlew nativeRun.

In the real-world, your application will, most likely, call either Java Reflection, Dynamic Proxy objects, or call some native code, or access resources on the class path - dynamic features that the native-image tool must be aware of at build time, and provided in the form of metadata. Native Image loads classes dynamically at build time, and not at run time.

Depending on your application dependencies, there are three ways to provide the metadata with the Native Image Gradle Plugin:

Using the Tracing Agent
Using the shared GraalVM Reachability Metadata Repository
Autodetecting (if the required resources are directly available on the classpath, in the src/main/resources directory)

For the Java application used in this guide the first two approaches are applicable. This guide demonstrates how to build a native executable with the Tracing agent and using the GraalVM Reachability Metadata Repository. The goal is to show users the difference, and prove how using shared metadata can simplify the work.

We recommend that you follow the instructions and create the application step-by-step. Alternatively, you can go right to the completed example.

You must have GraalVM installed with Native Image support.

Prepare a Demo Application

Create a new Java project with Gradle in your favorite IDE, called “H2Example”, in the org.graalvm.example package.

Rename the default app directory to H2Example, then rename the default filename App.java to H2Example.java and replace its contents with the following:

 package org.graalvm.example;

 import java.sql.Connection;
 import java.sql.DriverManager;
 import java.sql.PreparedStatement;
 import java.sql.ResultSet;
 import java.sql.SQLException;
 import java.util.ArrayList;
 import java.util.Comparator;
 import java.util.HashSet;
 import java.util.List;
 import java.util.Set;

 public class H2Example {

     public static final String JDBC_CONNECTION_URL = "jdbc:h2:./data/test";

     public static void main(String[] args) throws Exception {
         // Cleanup
         withConnection(JDBC_CONNECTION_URL, connection -> {
             connection.prepareStatement("DROP TABLE IF EXISTS customers").execute();
             connection.commit();
         });

         Set<String> customers = Set.of("Lord Archimonde", "Arthur", "Gilbert", "Grug");

         System.out.println("=== Inserting the following customers in the database: ");
         printCustomers(customers);

         // Insert data
         withConnection(JDBC_CONNECTION_URL, connection -> {
             connection.prepareStatement("CREATE TABLE customers(id INTEGER AUTO_INCREMENT, name VARCHAR)").execute();
             PreparedStatement statement = connection.prepareStatement("INSERT INTO customers(name) VALUES (?)");
             for (String customer : customers) {
                 statement.setString(1, customer);
                 statement.executeUpdate();
             }
             connection.commit();
         });

         System.out.println("");
         System.out.println("=== Reading customers from the database.");
         System.out.println("");

         Set<String> savedCustomers = new HashSet<>();
         // Read data
         withConnection(JDBC_CONNECTION_URL, connection -> {
             try (ResultSet resultSet = connection.prepareStatement("SELECT * FROM customers").executeQuery()) {
                 while (resultSet.next()) {
                     savedCustomers.add(resultSet.getObject(2, String.class));
                 }
             }
         });

         System.out.println("=== Customers in the database: ");
         printCustomers(savedCustomers);
     }

     private static void printCustomers(Set<String> customers) {
         List<String> customerList = new ArrayList<>(customers);
         customerList.sort(Comparator.naturalOrder());
         int i = 0;
         for (String customer : customerList) {
             System.out.println((i + 1) + ". " + customer);
             i++;
         }
     }

     private static void withConnection(String url, ConnectionCallback callback) throws SQLException {
         try (Connection connection = DriverManager.getConnection(url)) {
             connection.setAutoCommit(false);
             callback.run(connection);
         }
     }

     private interface ConnectionCallback {
         void run(Connection connection) throws SQLException;
     }
 }

Delete the H2Example/src/test/java directory.
Open the Gradle configuration file build.gradle, and update the main class in the application section:
```
 application {
     mainClass.set('org.graalvm.example.H2Example')
 }
```
Add explicit dependency on H2 Database, an open source SQL database for Java. The application interacts with this database through the JDBC driver. Insert the following line in the dependencies section of build.gradle:
```
 dependencies {
     implementation("com.h2database:h2:2.1.210")
 }
```
Also, in the dependencies section, remove the dependency on guava that will not be used.

The next steps will be focused what you should do to enable the Native Image Gradle plugin.
Register the Native Image Gradle plugin. Add the following to plugins section of your project’s build.gradle file:
```
 plugins {
 // ...
 id 'org.graalvm.buildtools.native' version '0.9.13'
 }
```
The plugin discovers which JAR files it needs to pass to the native-image builder and what the executable main class should be.
The plugin is not yet available on the Gradle Plugin Portal, so declare an additional plugin repository. Open the settings.gradle file and replace the default content with this:
```
 pluginManagement {
     repositories {
         mavenCentral()
         gradlePluginPortal()
     }
 }

 rootProject.name = 'H2Example'
 include('H2Example')
```
Note that the pluginManagement {} block must appear before any other statements in the file.

Build a Native Executable with the Agent

The Native Image Gradle plugin simplifies generation of the required metadata by injecting the Tracing agent (later the agent) automatically for you at compile time. To enable the agent, just pass the -Pagent option to any Gradle tasks that extends JavaForkOptions (for example, test or run).

The agent can run in multiple modes:

Standard: Collects metadata without conditions. This is recommended if you are building an executable.
Conditional: Collects metadata with conditions. This is recommended if you are creating conditional metadata for a library intended for further use.
Direct: For advanced users only. This mode allows directly controlling the command line passed to the agent.

You can configure the agent either passing the options on the command line, or in the build.gradle file. See below how to configure the Native Image Gradle plugin, collect metadata with the tracing agent, and build a native executable applying the provided configuration.

(Optional) Instruct the agent to run in the standard mode. Insert this configuration block at the bottom of the build.gradle file:
```
 graalvmNative {
     agent {
         defaultMode = "standard"
     }
     binaries {
         main {
             imageName.set('h2demo') 
         }
     }
     toolchainDetection = false
 }
```
If you prefer the command-lime option, that will be -Pagent=standard. The second part of the configuration shows how to specify a custom name for a final native executable.

Another thing to note here, the plugin may not be able to properly detect the GraalVM installation, because of limitations in Gradle. The workaround is to disable toolchain detection with this command: toolchainDetection = false. Learn more about selecting the GraalVM toolchain here.
Now run your application with the agent enabled, on the JVM:
```
 ./gradlew -Pagent run
```
The agent captures and writes down calls to the H2 Database and all the dynamic features encountered during a test run into multiple *-config.json files.
Once the metadata is collected, copy it into the project’s /META-INF/native-image directory using the metadataCopy task:
```
 ./gradlew metadataCopy --task run --dir src/main/resources/META-INF/native-image
```
The JSON files are stored in the META-INF/native-image/<group.id>/<artifact.id> project directory. It is not required but recommended that the output directory is /resources/META-INF/native-image/. The native-image tool will pick up metadata from that location automatically. For more information about how to collect metadata for your application automatically, see Collecting Metadata Automatically. Here is the expected files tree after this step:
Build a native executable using metadata acquired by the agent:
```
 ./gradlew nativeCompile
```
The native executable, named h2demo, is created in the build/native/nativeCompile directory.

Run the application from the native executable:

 ./H2Example/build/native/nativeCompile/h2demo

Learn more about using the agent with the Native Image Gradle plugin here.

Important: To proceed to the next section, clean up the project: ./gradlew clean. Make sure to delete META-INF and its contents.

Build a Native Executable Using the GraalVM Reachability Metadata Repository

Since release 0.9.11, the Native Image Gradle plugin adds experimental support for the GraalVM Reachability Metadata repository. This repository provides GraalVM configuration for libraries which do not support GraalVM Native Image by default. The support needs to be enabled explicitly.

Open the build.gradle file, and enable the GraalVM Reachability Metadata Repository in the graalvmNative plugin configuration:

 metadataRepository {
     enabled = true
 }

The whole configuration block should look like:

 graalvmNative {
     agent {
         defaultMode = "standard"
     }
     binaries {
         main {
             imageName.set('h2demo') 
         }
     }
     metadataRepository {
         enabled = true
     }
     toolchainDetection = false
 }

The plugin will automatically download the metadata from the repository.

Now build a native executable re-using metadata from the shared repository:
```
 ./gradlew nativeRun
```

Run the application from the native executable:

 ./H2Example/build/native/nativeCompile/h2demo

You are reaching the same results in less steps. Using the shared GraalVM Reachability Metadata Repository enhances the usability of Native Image for Java applications depending on 3rd party libraries.

Summary

The GraalVM Reachability Metadata Repository enables Native Image users to share and reuse metadata for libraries and frameworks in the Java ecosystem, and, thus share the burden of maintaining third-party dependencies.

Note that if your application does not call any dynamic features at run time, running the agent or enabling the GraalVM Reachability Metadata Repository is needless. Your workflow in that case would just be:

./gradlew nativeRun

Configure Native Image Using Shared Reachability Metadata

Prepare a Demo Application

Build a Native Executable with the Agent

Build a Native Executable Using the GraalVM Reachability Metadata Repository

Summary

Related Documentation