Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
diegovisentin opened this issue Sep 1, 2024 · 2 comments
Labels
kind/feature New feature or request
Milestone

Comments

@diegovisentin
Copy link

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

@diegovisentin diegovisentin added the kind/feature New feature or request label Sep 1, 2024
@squakez
Copy link
Contributor

squakez commented Sep 2, 2024

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
Copy link
Contributor

oscerd commented Sep 2, 2024

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.

@squakez squakez added this to the 2.6.0 milestone Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants