From a5a74d026684ad22f03fea305e7868f7a5406a75 Mon Sep 17 00:00:00 2001 From: Raphael <4246780+reitzig@users.noreply.github.com> Date: Mon, 17 Jun 2024 18:08:49 +0200 Subject: [PATCH] fix(docs): working link to manual of Native Image Maven Plugin --- first-party/jib-native-image-extension-maven/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/first-party/jib-native-image-extension-maven/README.md b/first-party/jib-native-image-extension-maven/README.md index 26aa66d..30ebc34 100644 --- a/first-party/jib-native-image-extension-maven/README.md +++ b/first-party/jib-native-image-extension-maven/README.md @@ -1,6 +1,6 @@ # Jib GraalVM Native Image Extension -This extension containerizes a [GraalVM native-imgae](https://www.graalvm.org/docs/reference-manual/native-image/) application configured with [Native Image Maven Plugin](https://www.graalvm.org/docs/reference-manual/native-image/#integration-with-maven). +This extension containerizes a [GraalVM native-imgae](https://www.graalvm.org/docs/reference-manual/native-image/) application configured with [Native Image Maven Plugin](https://graalvm.github.io/native-build-tools/latest/maven-plugin.html). The extension expects the `native-image-maven-plugin` to do the the heavy lifting of generating a "native image" (with the `native-image:native-image` goal). (The "image" in "native image" refers to an executable binary, not a container image.) Then the extension simply copies the binary, say, `/target/com.example.mymainclass`, into a container image and sets executable bits. It also auto-sets the container image entrypoint to the binary, say, `/app/com.example.mymainclass` (unless you manually configure `` in the main Jib configuration).