Repository navigation
Conversation
Camel core now requires Java 21, so the Kamelet libraries must be compiled for Java 21 as well. - root pom.xml: maven.compiler.source/target/release and the maven-compiler-plugin pluginManagement source/target set to 21 - camel-kamelets-catalog and kamelets-maven-plugin: compiler plugin source/target set to 21 - camel-kamelets-crds: maven.compiler.source/target/release set to 21 (<proc>full</proc> is kept, it is required since JDK 23) Co-authored-by: IBM Bob 2.2.1 Signed-off-by: Aurélien Pupier <apupier@ibm.com>
Camel core now requires Java 21, so CI, release and snapshot deployment must run on a Java 21 JDK instead of Java 17. - GitHub Actions (ci-build build and deploy jobs, validate, java-tests, main-push-regen, generate-sbom-main): setup-java version 17 -> 21 - integration-tests: the default JDK for the Maven build and the Citrus tests is now 21 (JDK 25 is still installed for the Camel JBang launcher); comments updated accordingly - jitpack.yml: openjdk17 -> openjdk21 - Jenkinsfile.deploy and Jenkinsfile.ppc64le: default JDK_NAME jdk_17_latest -> jdk_21_latest Co-authored-by: IBM Bob 2.2.1 Signed-off-by: Aurélien Pupier <apupier@ibm.com>
Camel core now requires Java 21, so the documented prerequisites are updated to match the build. - AGENTS.md (CLAUDE.md is a symlink to it): Java 17+ -> Java 21+ - tests/camel-kamelets-itest/README.md: required Java 17 -> Java 21 Co-authored-by: IBM Bob 2.2.1 Signed-off-by: Aurélien Pupier <apupier@ibm.com>
Add a breaking change entry to the Unreleased section: the minimal Java version is raised from 17 to 21, following Camel core, so the Kamelet libraries can no longer be used with Java 17. Co-authored-by: IBM Bob 2.2.1 Signed-off-by: Aurélien Pupier <apupier@ibm.com>
Contributor
|
We need a 4.23.0 release first |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Camel core now requires Java 21 (apache/camel#27943), so this PR raises the minimal Java version of the Kamelet Catalog from 17 to 21 (CAMEL-22996).
The change is split into one commit per area:
maven.compiler.source/target/releaseand themaven-compiler-pluginsource/targetset to 21 in the rootpom.xml,camel-kamelets-catalog,kamelets-maven-pluginandcamel-kamelets-crds.<proc>full</proc>in the CRDs module is kept (needed since JDK 23).ci-build(build + deploy),validate,java-tests,main-push-regen,generate-sbom-mainnow use Java 21.integration-tests: the default JDK for the Maven build and the Citrus tests is now 21; JDK 25 is still installed for the Camel JBang launcher.jitpack.yml:openjdk17→openjdk21.Jenkinsfile.deploy/Jenkinsfile.ppc64le:jdk_17_latest→jdk_21_latest.AGENTS.md(CLAUDE.mdis a symlink to it) andtests/camel-kamelets-itest/README.mdnow state Java 21.Why
The Kamelet libraries are consumed by Camel runtimes that now run on Java 21+. Keeping a Java 17 baseline is no longer useful.
Note: the baseline was already moved to 21 once (#2750, #2760) and reverted (#2780), because Camel core had gone back to 17 and downstream consumers hit class-version mismatches (65.0 vs 61.0). This PR must be merged only once the Camel version this repository depends on (
camel.version) is built for Java 21.Breaking change
The Kamelet libraries (
camel-kamelets,camel-kamelets-catalog,camel-kamelets-crds,kamelets-maven-plugin) are now compiled withrelease 21and can no longer be used with Java 17. The Kamelet YAML files are unchanged.Testing
./mvnw clean install -DskipTests -DskipITssucceeds; javac output shows[debug release 21]../mvnw verify -pl '!tests/camel-kamelets-itest'succeeds (catalog tests: 20 run, 0 failures).release 21(the local JDK 21 has nojavac).jdk_21_latestlabel on the ASF Jenkins agents and the JitPackopenjdk21build. Reviewers, please check that CI is green and that the Jenkins label exists.Checklist
nav.adoc/SBOM regeneration is neededCHANGELOG.mdupdatedDescription generated by IBM Bob 2.2.1 on behalf of Aurélien Pupier