From fbc50c721672e50c5427b6a7610aa36e1ef99ac5 Mon Sep 17 00:00:00 2001 From: Abdullah <89297042+AzazelSensei@users.noreply.github.com> Date: Fri, 14 Aug 2026 23:16:10 +0300 Subject: [PATCH] Drop the dead hawkeye example from the docs korandoru/hawkeye left Java for Rust, so the pom and hawkeye-cli links 404. Fixes #2505 --- docs/index.adoc | 4 ---- docs/index.html | 6 ------ 2 files changed, 10 deletions(-) diff --git a/docs/index.adoc b/docs/index.adoc index 70bcbf0a9..2e4fe01eb 100644 --- a/docs/index.adoc +++ b/docs/index.adoc @@ -13185,8 +13185,6 @@ This https://picocli.info/picocli-on-graalvm.html[older article], "Picocli on Gr See also this https://github.com/remkop/picocli-native-image-demo[demo Gradle project] and this https://github.com/remkop/picocli-native-image-maven-demo[demo Maven project] that provide a simple complete CLI app, with build instructions, that developers can clone, and build to get the stand-alone executable. -See also the http://github.com/korandoru/hawkeye[korandoru/hawkeye] for a real-world Maven project that provide a native image and a slim Docker image powered by native image. - [TIP] ==== Native images on Windows have the https://github.com/oracle/graal/issues/1762[problem] that the native image does not include the required dependency `msvcr100.dll` (for Java 8) or `VCRUNTIME140.dll` (with GraalVM 19.3 or later for Java 11). On Windows machines where this dependency is not in the `PATH`, the native image fails to start, and shows an error dialog "System Error: The program can't start because VCRUNTIME140.dll is missing from your computer". @@ -13211,8 +13209,6 @@ ____ The https://docs.spring.io/spring-boot/docs/current/maven-plugin/reference/htmlsingle/#packaging[Spring Boot Maven Plugin] provides a `repackage` goal to create executable archives that contain all of an application’s dependencies. It thus functions as an executable, is portable across operating systems and architectures, and is still a valid JAR file that can be executed explicitly or otherwise used as a JAR. -http://github.com/korandoru/hawkeye[korandoru/hawkeye] provides a real-world example to package a picocli application into an executable file. You can read the `pom.xml` file of https://github.com/korandoru/hawkeye/blob/main/hawkeye-cli/pom.xml[hawkeye-cli] module for details. Note that the default `embeddedLaunchScript.sh` assumes that the application may be a Spring Application while the hawkeye-cli example uses a customized tidy script. - === Really Executable JAR A https://skife.org/java/unix/2011/06/20/really_executable_jars.html[really executable JAR] diff --git a/docs/index.html b/docs/index.html index ad78112b7..8354a45f9 100644 --- a/docs/index.html +++ b/docs/index.html @@ -18478,9 +18478,6 @@

See also this demo Gradle project and this demo Maven project that provide a simple complete CLI app, with build instructions, that developers can clone, and build to get the stand-alone executable.

-
-

See also the korandoru/hawkeye for a real-world Maven project that provide a native image and a slim Docker image powered by native image.

-
@@ -18520,9 +18517,6 @@

The Spring Boot Maven Plugin provides a repackage goal to create executable archives that contain all of an application’s dependencies. It thus functions as an executable, is portable across operating systems and architectures, and is still a valid JAR file that can be executed explicitly or otherwise used as a JAR.

-
-

korandoru/hawkeye provides a real-world example to package a picocli application into an executable file. You can read the pom.xml file of hawkeye-cli module for details. Note that the default embeddedLaunchScript.sh assumes that the application may be a Spring Application while the hawkeye-cli example uses a customized tidy script.

-

29.5. Really Executable JAR