Dongjin Lee created KAFKA-12358:
-----------------------------------
Summary: Migrate to Java 11
Key: KAFKA-12358
URL: https://issues.apache.org/jira/browse/KAFKA-12358
Project: Kafka
Issue Type: Improvement
Reporter: Dongjin Lee
Assignee: Dongjin Lee
I found this problem when I was working on
[KAFKA-12324|https://issues.apache.org/jira/browse/KAFKA-12324].
As of present, Kafka Connect and Trogdor are using Jetty 9. Although Jetty's
stable release is 9.4, the Jetty community is now moving their focus to Jetty
10 and 11, which requires Java 11 as a prerequisite. To minimize potential
security vulnerability, Kafka should migrate into Java 11 + Jetty 11 as soon as
Jetty 9.4 reaches the end of life. As a note, [Jetty 9.2 reached End of Life in
March 2018|https://www.eclipse.org/lists/jetty-announce/msg00116.html] and 9.3
also did in [February
2020|https://www.eclipse.org/lists/jetty-announce/msg00140.html].
In other words, the necessity of moving to Java 11 is heavily affected by
Jetty's maintenance plan. Jetty 9.4 seems like still be supported for a certain
period of time, but it is worth being aware of these relationships and having a
migration plan beforehand.
For the java-scala compatibility, we have no issue. The recommended Scala
versions to Java 11 are 2.13.0 and 2.12.4, and we are already using the later
version. See:
https://docs.scala-lang.org/overviews/jdk-compatibility/overview.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
