slachiewicz opened a new pull request, #1783:
URL: https://github.com/apache/maven-mvnd/pull/1783

   Unblocks #1774 and any later jline bump on this line. jline 3.30.14+ 
resolves `openpty` through `SymbolLookup.libraryLookup`, and native-image 
supports that only from GraalVM 25 — the GraalVM docs for JDK 22 and JDK 24 
both list `loaderLookup()` as the only supported lookup, which is why all five 
GraalVM jobs on #1774 die in `CLibrary.<clinit>` with `Unsupported method 
jdk.internal.loader.NativeLibrary.findEntry0`.
   
   This ports what master needed for the same move (#1611, #1712), adapted to 
the 1.x layout (single `gcc` wrapper that picks the aarch64 redef by `uname`):
   
   - `JAVA_VERSION` 22 → 25 in `early-access.yaml` and `release.yaml`.
   - glibc patching: enumerate `lib/svm/clibraries` with `find` (GraalVM 25 
dropped `libjvm.a`/`liblibchelper.a`), add the `stat()` shim for glibc < 2.33 
and link it into `Scrt1.o`, and pin `stat` in both redef files. The `ldd` 
library-count check goes because `+StaticExecutableWithDynamicLibC` on GraalVM 
25 links only `libc.so`; the `objdump` GLIBC_ version check stays as the guard.
   - Test projects: Quarkus 3.35.3 / Java 17 in `type-description` and 
maven-invoker-plugin 3.10.1 in `invoker`, whose older Byte Buddy and Groovy 
reject JDK 25 class files.
   
   Kept `macos-15-intel`: Oracle publishes no GraalVM 25 macOS x64 build after 
25.0.1, but `25/latest` still serves 25.0.1 for x64, so the darwin-amd64 binary 
keeps building for now. Not ported from #1712: 
`--enable-native-access=ALL-UNNAMED` as the default `mvnd.jvmArgs`, because a 
1.x daemon may run on Java 8 where the flag is fatal.
   
   Verified: `./mvnw spotless:check` and `apache-rat:check` on JDK 21 → BUILD 
SUCCESS. The native build itself has only been run in CI.
   
   *This change was created with AI assistance.*


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to