This is an automated email from the ASF dual-hosted git repository. gnodet pushed a commit to branch backport/29465-to-camel-4.22.x in repository https://gitbox.apache.org/repos/asf/camel.git
commit 7ecd6934578be9c279884327d21af782a174afb5 Author: Guillaume Nodet <[email protected]> AuthorDate: Mon Nov 9 12:28:10 2026 +0000 [backport camel-4.22.x] chore: camel-launcher - enable native access in the manifest, so Java 24+ does not warn when JLine uses the FFM API --- dsl/camel-jbang/camel-launcher/pom.xml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/dsl/camel-jbang/camel-launcher/pom.xml b/dsl/camel-jbang/camel-launcher/pom.xml index 15b0a8b33ad3..b59db6e453f8 100644 --- a/dsl/camel-jbang/camel-launcher/pom.xml +++ b/dsl/camel-jbang/camel-launcher/pom.xml @@ -305,6 +305,19 @@ <build> <plugins> + <!-- the repackaged self-executing JAR keeps this manifest --> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-jar-plugin</artifactId> + <configuration> + <archive> + <manifestEntries> + <!-- JLine uses the FFM API for the terminal (JEP 472: Java 24+ warns without it) --> + <Enable-Native-Access>ALL-UNNAMED</Enable-Native-Access> + </manifestEntries> + </archive> + </configuration> + </plugin> <!-- Create self-executing JAR using Spring Boot loader tools --> <plugin> <groupId>org.apache.camel</groupId>
