[jira] [Updated] (KAFKA-7264) Support Java 11
[ https://issues.apache.org/jira/browse/KAFKA-7264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-7264: Fix Version/s: (was: 2.1.0) 2.2.0 > Support Java 11 > --- > > Key: KAFKA-7264 > URL: https://issues.apache.org/jira/browse/KAFKA-7264 > Project: Kafka > Issue Type: Improvement >Reporter: Ismael Juma >Priority: Major > Fix For: 2.2.0 > > > Java 11 is the next LTS release and it should be released by the end of > September. Kafka should ideally support that in the 2.1.0 release. A few > known issues/requirements have been captured via subtasks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KAFKA-7264) Support Java 11
[ https://issues.apache.org/jira/browse/KAFKA-7264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7264: --- Description: Java 11 is the next LTS release and it should be released by the end of September. Kafka should ideally support that in the 2.1.0 release. A few known issues/requirements have been captured via subtasks. (was: Java 11 is the next LTS release and it should be released by the end of September. Kafka should ideally support that in the 2.1.0 release. A few known issues/requirements.) > Support Java 11 > --- > > Key: KAFKA-7264 > URL: https://issues.apache.org/jira/browse/KAFKA-7264 > Project: Kafka > Issue Type: Improvement >Reporter: Ismael Juma >Priority: Major > Fix For: 2.1.0 > > > Java 11 is the next LTS release and it should be released by the end of > September. Kafka should ideally support that in the 2.1.0 release. A few > known issues/requirements have been captured via subtasks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KAFKA-7264) Support Java 11
[ https://issues.apache.org/jira/browse/KAFKA-7264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7264: --- Description: Java 11 is the next LTS release and it should be released by the end of September. Kafka should ideally support that in the 2.1.0 release. A few known issues/requirements. (was: Java 11 is the next LTS release and it should be released by the end of September. Kafka should ideally support that in the 2.1.0 release. A few known issues/requirements: * A new version of EasyMock with a new version of cglib and ASM7_EXPERIMENTAL (or ASM7 when Java 11 ships) enabled (both projects have the necessary code changes, but they are not included in released versions). * The rat and checkstyle gradle plugin configuration rely on the ability to mutate user.dir, but that's not allowed in Java 11. So they fail. * A new version of Jacoco is needed, the changes required are not in a released version yet. * Many SSL tests in clients fail. Probably related to the TLS 1.3 changes in Java 11. * Many SSL (and some SASL) tests in Core fail. Maybe same underlying reason as the clients failures, but I didn't investigate.) > Support Java 11 > --- > > Key: KAFKA-7264 > URL: https://issues.apache.org/jira/browse/KAFKA-7264 > Project: Kafka > Issue Type: Improvement >Reporter: Ismael Juma >Priority: Major > Fix For: 2.1.0 > > > Java 11 is the next LTS release and it should be released by the end of > September. Kafka should ideally support that in the 2.1.0 release. A few > known issues/requirements. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KAFKA-7264) Support Java 11
[ https://issues.apache.org/jira/browse/KAFKA-7264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-7264: --- Description: Java 11 is the next LTS release and it should be released by the end of September. Kafka should ideally support that in the 2.1.0 release. A few known issues/requirements: * A new version of EasyMock with a new version of cglib and ASM7_EXPERIMENTAL (or ASM7 when Java 11 ships) enabled (both projects have the necessary code changes, but they are not included in released versions). * The rat and checkstyle gradle plugin configuration rely on the ability to mutate user.dir, but that's not allowed in Java 11. So they fail. * A new version of Jacoco is needed, the changes required are not in a released version yet. * Many SSL tests in clients fail. Probably related to the TLS 1.3 changes in Java 11. * Many SSL (and some SASL) tests in Core fail. Maybe same underlying reason as the clients failures, but I didn't investigate. was: Java 11 is the next LTS release and it should be released by the end of September. Kafka should ideally support that in the 2.1.0 release. A few known issues/requirements: * A new version of EasyMock with a new version of cglib and ASM7_EXPERIMENTAL (or ASM7 when Java 11 ships) enabled (both projects have the necessary code changes, but they are not included in released versions). * The rat and checkstyle gradle plugins rely on the ability to mutate user.dir, but that's not allowed in Java 11. So they fail. * A new version of Jacoco is needed, the changes required are not in a released version yet. * Many SSL tests in clients fail. Probably related to the TLS 1.3 changes in Java 11. * Many SSL (and some SASL) tests in Core fail. Maybe same underlying reason as the clients failures, but I didn't investigate. > Support Java 11 > --- > > Key: KAFKA-7264 > URL: https://issues.apache.org/jira/browse/KAFKA-7264 > Project: Kafka > Issue Type: Improvement >Reporter: Ismael Juma >Priority: Major > Fix For: 2.1.0 > > > Java 11 is the next LTS release and it should be released by the end of > September. Kafka should ideally support that in the 2.1.0 release. A few > known issues/requirements: > * A new version of EasyMock with a new version of cglib and ASM7_EXPERIMENTAL > (or ASM7 when Java 11 ships) enabled (both projects have the necessary code > changes, but they are not included in released versions). > * The rat and checkstyle gradle plugin configuration rely on the ability to > mutate user.dir, but that's not allowed in Java 11. So they fail. > * A new version of Jacoco is needed, the changes required are not in a > released version yet. > * Many SSL tests in clients fail. Probably related to the TLS 1.3 changes in > Java 11. > * Many SSL (and some SASL) tests in Core fail. Maybe same underlying reason > as the clients failures, but I didn't investigate. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
