Every component (like the builder) should use Java 21 as it is the current LTS version

[diegovisentin]

Requirement

See subject

Problem

Java 21 has been available for a year now and I think it is important to keep this framework updated on a reasonable basis.

Proposal

No response

Open questions

No response

[squakez]

It's reasonable. Right now the equipment of JDK is hardcoded in the operator container image (from which it is inherited). We probably need to develop some mechanism to let the user choose which JDK to use or to distribute more container images with different JDKs.

[oscerd]

JDK 21 is supported to run Camel applications. Basically Camel 4.x is still built and released with JDK 17. So the LTS versions could run with JDK 21 (we have CI job for this), but the Java used to build and release the LTS is the JDK 17.

[github-actions[bot]]

This issue has been automatically marked as stale due to 90 days of inactivity. It will be closed if no further activity occurs within 15 days. If you think that’s incorrect or the issue should never stale, please simply write any comment. Thanks for your contributions!

[squakez]

@diegovisentin you can test this using the JDK21 container image in nightly release in https://hub.docker.com/r/testcamelk/camel-k/tags - upcoming 2.6.0 will be provided with JDK21 as well, feel free to run a round of tests and let us know.