Hi all, After upgrading Apache Karaf to version 4.4.9, we are encountering the following build-time error when compiling on JDK 17:
Restricted to JDK 17, yet org.jline:jline:jar:3.30.6:compile contains org/jline/terminal/impl/ffm/CLibrary$termios.class targeted to JDK 22 We have the maven-enforcer-plugin configured with: <maxJdkVersion>17</maxJdkVersion> and it reports invalid class files coming from the JLine dependency. I noticed that the JLine project mentions the following warning in its documentation: Note: The FFM terminal provider (jline-terminal-ffm) requires JDK 22+ and native access permissions. >From what I can tell, the JDK 22–specific classes are related to the FFM terminal provider. We are not using this provider at runtime. My question is: Is it safe to ignore this warning (or relax the enforcer rule) if the FFM terminal provider is not used, or is there a recommended way to exclude or handle these JDK 22–specific classes when building Karaf on JDK 17? Any guidance or best practices would be appreciated. Thanks in advance, Steven Huypens On Mon, Dec 15, 2025 at 10:00 AM Jean-Baptiste Onofré <[email protected]> wrote: > The Karaf team is pleased to announce Apache Karaf runtime 4.4.9 release. > > Apache Karaf runtime 4.4.9 is a maintenance release, bringing a lot of > dependency updates and fixes, especially: > * provide karaf-integration distribution > * fix on the log service when using logback backend > * upgrade to the latest JLine version, fixing a CVE > * support array in configuration property passed via env variable or > system property > * fix on the karaf-maven-plugin dealing with packaging type in features > and kar > > You can take a look on the Release Notes for details: > https://github.com/apache/karaf/releases/tag/karaf-4.4.9 > > You can download Apache Karaf runtime 4.4.0 from: > https://karaf.apache.org/download.html > > Enjoy! > The Apache Karaf team >
