-
Couldn't load subscription status.
- Fork 634
Remove support for Java 11 #2308
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
Conversation
1. Why: Jetty 12 requires a minimum of Java 17, so Java 11 must be dropped to facilitate this upgrade. The current version of Jetty in cruise-control is 9.4.56.v20240826. This version contains two CVEs CVE-2024-13009 - patched in 9.4.57.v20241219 CVE-2024-6763 - patched in 12.0.12 So, Jetty 12 is need to patch CVE-2024-6763. 2. What: Remove support support for Java 11 Raise minimum JDK to 17 in builds, docs, and workflows - [x] refactor Signed-off-by: JvD_Ericsson <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In hindsight, I wish we had added a deprecation notice for Java 11 when we added support for Java 17 some months back. That being said, dropping Java 11 now is a reasonable step especially given that it's required to address certain CVEs (some listed in the PR description) and to support newer Kafka versions (Kafka >= 4.0).
As far as backward compatibility is concerned, Java 17 has been supported in Kafka since version 3.2.0 [1]. Although Cruise Control’s main branch currently only supports Kafka >= 3.7.0, it’s still important to maintain compatibility with as many Kafka versions as possible to serve the broadest range of users in the community. So this change is in line with that goal as well.
I have tested this change and have been running builds with Java 17 for some time now, this looks like a reasonable update to me. We just need a maintainer to sign off and merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the change. LGTM.
1. Why: Jetty 12 requires a minimum of Java 17, so Java 11 must be dropped to facilitate this upgrade. The current version of Jetty in cruise-control is 9.4.56.v20240826. This version contains two CVEs CVE-2024-13009 - patched in 9.4.57.v20241219 CVE-2024-6763 - patched in 12.0.12 So, Jetty 12 is need to patch CVE-2024-6763. 2. What: Remove support support for Java 11 Raise minimum JDK to 17 in builds, docs, and workflows - [x] refactor Signed-off-by: JvD_Ericsson <[email protected]>
1. Why: Jetty 12 requires a minimum of Java 17, so Java 11 must be dropped to facilitate this upgrade. The current version of Jetty in cruise-control is 9.4.56.v20240826. This version contains two CVEs CVE-2024-13009 - patched in 9.4.57.v20241219 CVE-2024-6763 - patched in 12.0.12 So, Jetty 12 is need to patch CVE-2024-6763. 2. What: Remove support support for Java 11 Raise minimum JDK to 17 in builds, docs, and workflows - [x] refactor Signed-off-by: JvD_Ericsson <[email protected]>
Summary
So, Jetty 12 is needed to patch CVE-2024-6763.
Categorization