From d84c5cbfc7a636981c9b092c36ee61cc43980465 Mon Sep 17 00:00:00 2001 From: DemchaAV Date: Fri, 29 May 2026 09:26:02 +0100 Subject: [PATCH] ci(jitpack): pin JDK 17 and scope install to the library module JitPack built on openjdk21 while the release verify/javadoc gate runs on JDK 17 (the project's maven.compiler.release baseline), so the published jar was built on a JDK that CI does not validate. Pin JitPack to openjdk17 to remove that drift, and scope the install to `-pl .` so only the library artifact is built, never the examples/benchmarks reactor siblings. --- jitpack.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/jitpack.yml b/jitpack.yml index 635724a6..503c23c3 100644 --- a/jitpack.yml +++ b/jitpack.yml @@ -1,4 +1,14 @@ +# JitPack builds the published library artifact +# (com.github.DemchaAV:GraphCompose) from the standalone root pom.xml. +# +# JDK is pinned to 17 — the project's compile baseline +# (maven.compiler.release=17) and the JDK the release verify/javadoc gate +# runs on — so the jar consumers download is built on the same JDK CI +# validates, not a drifting newer one. +# +# install is scoped to the root module (-pl .) so JitPack builds only the +# library, never the examples/benchmarks reactor siblings. jdk: - - openjdk21 + - openjdk17 install: - - ./mvnw -DskipTests install + - ./mvnw -DskipTests install -pl .