flasn4nt
/
graal
mirror of https://github.com/oracle/graal.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[GR-59533] Test and refresh Include Reachability Metadata Native Image guides. 

PullRequest: graal/19219
This commit is contained in:
Olya Gupalo 2024-11-07 21:27:43 +00:00
parent f3d5274aca 509a73e1bf
commit 3bf288d174
2 changed files with 53 additions and 134 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

93
docs/reference-manual/native-image/guides/include-reachability-metadata-gradle.md
View File

@ -27,7 +27,7 @@ Alternatively, you can go right to the [completed example](https://github.com/gr
## Prepare a Demo Application
> Note: A Java version between 17 and 20 is required to execute Gradle (see the [Gradle Compatibility Matrix](https://docs.gradle.org/current/userguide/compatibility.html)). However, if you want to run your application with Java 21 (or higher), there is a workaround: set `JAVA_HOME` to a Java version between 17 and 20, and `GRAALVM_HOME` to GraalVM for JDK 21. See the [Native Image Gradle Plugin documentation](https://graalvm.github.io/native-build-tools/latest/gradle-plugin.html#_installing_graalvm_native_image_tool) for more details.
> Note: A Java version between 17 and 21 is required to execute Gradle (see the [Gradle Compatibility Matrix](https://docs.gradle.org/current/userguide/compatibility.html)). However, if you want to run your application with Java 23 (or higher), there is a workaround: set `JAVA_HOME` to a Java version between 17 and 21, and `GRAALVM_HOME` to GraalVM for JDK 23. See the [Native Image Gradle Plugin documentation](https://graalvm.github.io/native-build-tools/latest/gradle-plugin.html#_installing_graalvm_native_image_tool) for more details.
### Prerequisite
Make sure you have installed a GraalVM JDK.
@ -56,7 +56,6 @@ For other installation options, visit the [Downloads section](https://www.graalv
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();
@ -67,7 +66,6 @@ For other installation options, visit the [Downloads section](https://www.graalv
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 (?)");
@ -83,7 +81,6 @@ For other installation options, visit the [Downloads section](https://www.graalv
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()) {
@ -119,14 +116,12 @@ For other installation options, visit the [Downloads section](https://www.graalv
}
```
3. Delete the _H2Example/src/test/java/_ directory (if it exists).
4. Open the Gradle configuration file _build.gradle_, and replace its contents with the following:
3. Open the Gradle configuration file _build.gradle_, and replace its contents with the following:
```
plugins {
id 'application'
// 1. Native Image Gradle plugin
id 'org.graalvm.buildtools.native' version '0.10.1'
id 'org.graalvm.buildtools.native' version '0.10.3'
}
repositories {
@ -145,9 +140,6 @@ For other installation options, visit the [Downloads section](https://www.graalv
// 4. Native Image build configuration
graalvmNative {
agent {
defaultMode = "standard"
}
binaries {
main {
imageName.set('h2example')
@ -164,9 +156,9 @@ For other installation options, visit the [Downloads section](https://www.graalv
**3** Add a dependency on the [H2 Database](https://www.h2database.com/html/main.html), an open source SQL database for Java. The application interacts with this database through the JDBC driver.
**4** You can pass parameters to the `native-image` tool in the `graalvmNative` plugin configuration. In individual `buildArgs` you can pass parameters exactly the same way as you do from a command line. The `-Ob` option to enable quick build mode (recommended during development only) is used as an example. `imageName.set()` is used to specify the name for the resulting binary. Learn about other configuration options from the [plugin's documentation](https://graalvm.github.io/native-build-tools/latest/gradle-plugin.html#configuration).
**4** You can pass parameters to the `native-image` tool in the `graalvmNative` plugin configuration. In individual `buildArgs` you can pass parameters exactly the same way as you do on the command line. The `-Ob` option to enable the quick build mode (recommended during development only) is used as an example. `imageName.set()` is used to specify the name for the resulting binary. Learn about other configuration options from the [plugin's documentation](https://graalvm.github.io/native-build-tools/latest/gradle-plugin.html#configuration).
5. 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:
4. 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 {
@ -180,53 +172,26 @@ For other installation options, visit the [Downloads section](https://www.graalv
```
Note that the `pluginManagement {}` block must appear before any other statements in the file.
6. (Optional) Build the application. From the root directory of the repository, run the following command:
5. (Optional) Build and run the application:
```shell
./gradlew run
gradle run
```
This generates an "executable" JAR file, one that contains all of the application's dependencies and also a correctly configured _MANIFEST_ file.
This generates a runnable JAR file that returns a list of customers stored in the H2 Database.
## Build a Native Executable Using the GraalVM Reachability Metadata Repository
The Native Image Gradle plugin provides support for the [GraalVM Reachability Metadata repository](https://github.com/oracle/graalvm-reachability-metadata).
This repository provides GraalVM configuration for libraries which do not support GraalVM Native Image by default.
[GraalVM Reachability Metadata repository](https://github.com/oracle/graalvm-reachability-metadata) provides GraalVM configuration for libraries which do not support GraalVM Native Image by default.
One of these is the [H2 Database](https://www.h2database.com/html/main.html) this application depends on.
The support needs to be enabled explicitly.
1. 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('h2example')
buildArgs.add("-Ob")
}
}
metadataRepository {
enabled = true
}
}
```
The plugin automatically downloads the metadata from the repository.
The Native Image Gradle plugin **automatically downloads the metadata from the repository at build time**.
2. Now build a native executable using the metadata:
With Gradle you can build a native executable and run it at one step:
```shell
./gradlew nativeRun
gradle nativeRun
```
This generates a native executable for the platform in the _build/native/nativeCompile/_ directory, called `h2example`.
The native executable, named _h2example_, is created in the _build/native/nativeCompile_ directory.
The command also runs the application from that native executable.
Using the GraalVM Reachability Metadata Repository enhances the usability of Native Image for Java applications depending on 3rd party libraries.
## Build a Native Executable with the Tracing Agent
The second way to provide the medatata configuration for `native-image` is by injecting the [Tracing Agent](https://graalvm.github.io/native-build-tools/latest/gradle-plugin.html#agent-support) (later *the agent*) at compile time.
@ -237,54 +202,42 @@ The agent can run in three modes:
- **Direct**: For advanced users only. This mode allows directly controlling the command line passed to the agent.
You can configure the agent by either passing the options on the command line, or in the _build.gradle_ file.
See below how to collect metadata with the Tracing Agent, and build a native executable applying the provided configuration.
See below how to collect metadata with the agent, and build a native executable.
1. Open the _build.gradle_ file and see the agent mode specified in the `graalvmNative` plugin configuration:
1. Open the _build.gradle_ file and add the agent configuration in the `graalvmNative` block:
```
graalvmNative {
agent {
defaultMode = "standard"
}
...
}
```
It defines which mode the agent should run on.
If you prefer the command-lime option, it is `-Pagent=standard`.
2. Now run your application with the agent, on the JVM. To enable the agent with the Native Image Gradle plugin, pass the `-Pagent` option to any Gradle tasks that extends `JavaForkOptions` (for example, `test` or `run`):
```shell
./gradlew -Pagent run
gradle -Pagent run
```
The agent captures and records calls to the H2 Database and all the dynamic features encountered during a test run into multiple _*-config.json_ files.
The agent captures and records calls to the H2 Database and all the dynamic features encountered during a test run into the JSON file(s) in the _/build/native/agent-output/run_ directory.
3. Once the metadata is collected, copy it into the project's _/META-INF/native-image/_ directory using the `metadataCopy` task:
```shell
./gradlew metadataCopy --task run --dir src/main/resources/META-INF/native-image
gradle metadataCopy --task run --dir src/main/resources/META-INF/native-image
```
It is not required but recommended that the output directory is _/resources/META-INF/native-image/_. The `native-image` tool picks up metadata from that location automatically. For more information about how to collect metadata for your application automatically, see [Collecting Metadata Automatically](../AutomaticMetadataCollection.md).
4. Build a native executable using configuration collected by the agent:
```shell
./gradlew nativeCompile
gradle nativeRun
```
The native executable, named _h2example_, is created in the _build/native/nativeCompile_ directory.
The command also runs the application.
5. Run the application from the native executable:
```shell
./build/native/nativeCompile/h2example
```
6. (Optional) To clean up the project, run `./gradlew clean`, and delete the directory _META-INF_ with its contents.
5. (Optional) To clean up the project, run `gradle clean`, and delete the directory _META-INF_ with its contents.
### Summary
This guide demonstrated how to build a native executable using the [GraalVM Reachability Metadata Repository](https://github.com/oracle/graalvm-reachability-metadata) and with the Tracing Agent. The goal was to show the difference, and prove how using the reachability metadata can simplify the work.
Note that if your application does not call any dynamic features at run time, enabling the GraalVM Reachability Metadata Repository is needless.
Your workflow in that case would just be:
```shell
./gradlew nativeRun
```
Using the GraalVM Reachability Metadata Repository enhances the usability of Native Image for Java applications depending on 3rd party libraries.
### Related Documentation

76
docs/reference-manual/native-image/guides/include-reachability-metadata-maven.md
View File

@ -54,7 +54,6 @@ For other installation options, visit the [Downloads section](https://www.graalv
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();
@ -65,7 +64,6 @@ For other installation options, visit the [Downloads section](https://www.graalv
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 (?)");
@ -81,7 +79,6 @@ For other installation options, visit the [Downloads section](https://www.graalv
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()) {
@ -116,9 +113,8 @@ For other installation options, visit the [Downloads section](https://www.graalv
}
}
```
3. Delete the _H2Example/src/test/java/_ directory (if it exists).
4. Open the project configuration file, _pom.xml_, and replace its contents with the following:
3. Open the project configuration file, _pom.xml_, and replace its contents with the following:
```xml
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
@ -132,8 +128,6 @@ For other installation options, visit the [Downloads section](https://www.graalv
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<h2.version>2.2.220</h2.version>
<!-- Replace with your Java version -->
<java.version>22</java.version>
<imageName>h2example</imageName>
<mainClass>org.graalvm.example.H2Example</mainClass>
</properties>
@ -155,7 +149,7 @@ For other installation options, visit the [Downloads section](https://www.graalv
<plugin>
<groupId>org.graalvm.buildtools</groupId>
<artifactId>native-maven-plugin</artifactId>
<version>0.10.1</version>
<version>0.10.3</version>
<extensions>true</extensions>
<executions>
<execution>
@ -243,55 +237,36 @@ For other installation options, visit the [Downloads section](https://www.graalv
```
**1** Add a dependency on the [H2 Database](https://www.h2database.com/html/main.html), an open source SQL database for Java. The application interacts with this database through the JDBC driver.
**2** Enable the [Native Image Maven plugin](https://graalvm.github.io/native-build-tools/latest/maven-plugin.html) within a Maven profile, attached to the `package` phase.
(You are going to build a native executable using a Maven profile.) A Maven profile allows you to decide whether to just build a JAR file, or a native executable.
The plugin discovers which JAR files it needs to pass to `native-image` and what the executable main class should be.
**2** Enable the [Native Image Maven plugin](https://graalvm.github.io/native-build-tools/latest/maven-plugin.html) within a Maven profile, attached to the `package` phase. You are going to build a native executable using a Maven profile. A Maven profile allows you to decide whether to just build a JAR file, or a native executable. The plugin discovers which JAR files it needs to pass to `native-image` and what the executable main class should be.
**3** You can pass parameters to the underlying `native-image` build tool using the `<buildArgs>` section. In individual `<buildArg>` tags you can pass parameters exactly the same way as you do from a command line. The `-Ob` option to enable quick build mode (recommended during development only) is used as an example. Learn about other configuration options from the [plugin's documentation](https://graalvm.github.io/native-build-tools/latest/maven-plugin.html#configuration-options).
5. (Optional) Build the application. From the root directory of the repository, run the following command:
```shell
mvn clean package
**3** You can pass parameters to the underlying `native-image` build tool using the `<buildArgs>` section. In individual `<buildArg>` tags you can pass parameters exactly the same way as you do on the command line. The `-Ob` option to enable the quick build mode (recommended during development only) is used as an example. Learn about other configuration options from the [plugin's documentation](https://graalvm.github.io/native-build-tools/latest/maven-plugin.html#configuration-options).
4. (Optional) Build the application:
```
This generates an "executable" JAR file, one that contains all of the application's dependencies and also a correctly configured _MANIFEST_ file.
mvn -DskipTests clean package
```
This generates an executable JAR file.
## Build a Native Executable Using the GraalVM Reachability Metadata Repository
The Native Image Maven plugin provides support for the [GraalVM Reachability Metadata repository](https://github.com/oracle/graalvm-reachability-metadata).
This repository provides GraalVM configuration for libraries which do not support GraalVM Native Image by default.
[GraalVM Reachability Metadata repository](https://github.com/oracle/graalvm-reachability-metadata) provides GraalVM configuration for libraries which do not support GraalVM Native Image by default.
One of these is the [H2 Database](https://www.h2database.com/html/main.html) this application depends on.
The support needs to be enabled explicitly.
1. Open _pom.xml_, and include the following into the `<configuration>` element of the `native` profile to enable the GraalVM Reachability Metadata Repository:
```xml
<metadataRepository>
<enabled>true</enabled>
</metadataRepository>
```
The configuration block should resemble this:
```xml
<configuration>
<buildArgs>
<buildArg>-Ob</buildArg>
</buildArgs>
<metadataRepository>
<enabled>true</enabled>
</metadataRepository>
</configuration>
```
The plugin automatically downloads the metadata from the repository.
The Native Image Maven plugin **automatically downloads the metadata from the repository at build time**.
2. Now build a native executable using the profile (note that the profile name is specified with the `-P` flag):
1. Build a native image:
```shell
mvn package -Pnative
mvn -DskipTests -Pnative package
```
This generates a native executable for the platform in the _target/_ directory, called `h2example`.
3. Run the application from the native executable:
This generates an executable file for the platform in the _target/_ directory, called `h2example`.
Notice the new directory _target/graalvm-reachability-metadata_ where the metadata is pulled into.
2. Run the application from the native executable which should return a list of customers stored in the H2 Database:
```shell
./target/h2example
```
The application returns a list of customers stored in the H2 Database.
3. Run `mvn clean` to clean up the project and delete the metadata directory with its contents before you continue.
## Build a Native Executable with the Tracing Agent
@ -304,6 +279,7 @@ The agent can run in three modes:
- **Direct**: For advanced users only. This mode allows directly controlling the command line passed to the agent.
See below how to collect metadata with the Tracing Agent, and build a native executable applying the provided configuration.
Before you continue, clean the project from the previous build: `mvn clean`.
1. Enable the agent by adding the following into the `<configuration>` element of the `native` profile:
```xml
@ -320,9 +296,6 @@ See below how to collect metadata with the Tracing Agent, and build a native exe
<buildArgs>
<buildArg>-Ob</buildArg>
</buildArgs>
<metadataRepository>
<enabled>true</enabled>
</metadataRepository>
</configuration>
```
@ -358,7 +331,7 @@ In the `native` Maven profile section, add the `exec-maven-plugin` plugin:
```shell
mvn -Pnative -Dagent=true -DskipTests -DskipNativeBuild=true package exec:exec@java-agent
```
The agent captures and records calls to the H2 Database and all the dynamic features encountered during a test run into multiple _*-config.json_ files in the _target/native/agent-output/main/_ directory.
The agent captures and records calls to the H2 Database and all the dynamic features encountered during a test run into the _reachability-metadata.json_ file in the _target/native/agent-output/main/_ directory.
4. Build a native executable using configuration collected by the agent:
```shell
@ -371,17 +344,10 @@ In the `native` Maven profile section, add the `exec-maven-plugin` plugin:
./target/h2example
```
6. (Optional) To clean up the project, run `mvn clean`, and delete the directory _META-INF/_ with its contents.
### Summary
This guide demonstrated how to build a native executable using the [GraalVM Reachability Metadata Repository](https://github.com/oracle/graalvm-reachability-metadata) and with the Tracing Agent. The goal was to show the difference, and prove how using the reachability metadata can simplify the work.
Note that if your application does not call any dynamic features at run time, enabling the GraalVM Reachability Metadata Repository is needless.
Your workflow in that case would just be:
```shell
mvn package -Pnative
```
Using the GraalVM Reachability Metadata Repository enhances the usability of Native Image for Java applications depending on 3rd party libraries.
### Related Documentation