[jira] [Updated] (KAFKA-15208) Upgrade Jackson dependencies to version 2.15.6
[ https://issues.apache.org/jira/browse/KAFKA-15208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA updated KAFKA-15208: --- Description: Upgrading the version of Jackson dependencies to the latest stable version 2.16.0 can bring much bug fixing security issues solving and performance improvement Check release notes back to the current version [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.16.0] [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14] was: Upgrading the version of Jackson dependencies to the latest stable version 2.15.2 can bring much bug fixing security issues solving and performance improvement Check release notes back to the current version [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.15.3] [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14] > Upgrade Jackson dependencies to version 2.15.6 > -- > > Key: KAFKA-15208 > URL: https://issues.apache.org/jira/browse/KAFKA-15208 > Project: Kafka > Issue Type: Improvement > Components: connect, kraft >Reporter: Said BOUDJELDA >Assignee: Said BOUDJELDA >Priority: Major > Labels: dependencies > Fix For: 3.7.0 > > > Upgrading the version of Jackson dependencies to the latest stable version > 2.16.0 can bring much bug fixing security issues solving and performance > improvement > > Check release notes back to the current version > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.16.0] > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14] > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15208) Upgrade Jackson dependencies to version 2.16.0
[ https://issues.apache.org/jira/browse/KAFKA-15208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA updated KAFKA-15208: --- Summary: Upgrade Jackson dependencies to version 2.16.0 (was: Upgrade Jackson dependencies to version 2.15.6) > Upgrade Jackson dependencies to version 2.16.0 > -- > > Key: KAFKA-15208 > URL: https://issues.apache.org/jira/browse/KAFKA-15208 > Project: Kafka > Issue Type: Improvement > Components: connect, kraft >Reporter: Said BOUDJELDA >Assignee: Said BOUDJELDA >Priority: Major > Labels: dependencies > Fix For: 3.7.0 > > > Upgrading the version of Jackson dependencies to the latest stable version > 2.16.0 can bring much bug fixing security issues solving and performance > improvement > > Check release notes back to the current version > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.16.0] > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14] > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15208) Upgrade Jackson dependencies to version 2.15.6
[ https://issues.apache.org/jira/browse/KAFKA-15208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA updated KAFKA-15208: --- Summary: Upgrade Jackson dependencies to version 2.15.6 (was: Upgrade Jackson dependencies to version 2.15.3) > Upgrade Jackson dependencies to version 2.15.6 > -- > > Key: KAFKA-15208 > URL: https://issues.apache.org/jira/browse/KAFKA-15208 > Project: Kafka > Issue Type: Improvement > Components: connect, kraft >Reporter: Said BOUDJELDA >Assignee: Said BOUDJELDA >Priority: Major > Labels: dependencies > Fix For: 3.7.0 > > > Upgrading the version of Jackson dependencies to the latest stable version > 2.15.2 can bring much bug fixing security issues solving and performance > improvement > > Check release notes back to the current version > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.15.3] > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14] > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KAFKA-15208) Upgrade Jackson dependencies to version 2.15.3
[ https://issues.apache.org/jira/browse/KAFKA-15208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17775070#comment-17775070 ] Said BOUDJELDA commented on KAFKA-15208: This JIRA is updated to mention an upgrade to version 1.15.3 that comes to bring more bug fixing and enhancements Pleass to the last release notes https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.15.3 for more information > Upgrade Jackson dependencies to version 2.15.3 > -- > > Key: KAFKA-15208 > URL: https://issues.apache.org/jira/browse/KAFKA-15208 > Project: Kafka > Issue Type: Improvement > Components: connect, kraft >Reporter: Said BOUDJELDA >Assignee: Said BOUDJELDA >Priority: Major > Labels: dependencies > Fix For: 3.7.0 > > > Upgrading the version of Jackson dependencies to the latest stable version > 2.15.2 can bring much bug fixing security issues solving and performance > improvement > > Check release notes back to the current version > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.15.3] > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14] > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15208) Upgrade Jackson dependencies to version 2.15.3
[ https://issues.apache.org/jira/browse/KAFKA-15208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA updated KAFKA-15208: --- Description: Upgrading the version of Jackson dependencies to the latest stable version 2.15.2 can bring much bug fixing security issues solving and performance improvement Check release notes back to the current version [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.15.3] [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14] was: Upgrading the version of Jackson dependencies to the latest stable version 2.15.2 can bring much bug fixing security issues solving and performance improvement Check release notes back to the current version [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.15.2] [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14] > Upgrade Jackson dependencies to version 2.15.3 > -- > > Key: KAFKA-15208 > URL: https://issues.apache.org/jira/browse/KAFKA-15208 > Project: Kafka > Issue Type: Improvement > Components: connect, kraft >Reporter: Said BOUDJELDA >Assignee: Said BOUDJELDA >Priority: Major > Labels: dependencies > Fix For: 3.7.0 > > > Upgrading the version of Jackson dependencies to the latest stable version > 2.15.2 can bring much bug fixing security issues solving and performance > improvement > > Check release notes back to the current version > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.15.3] > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14] > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15208) Upgrade Jackson dependencies to version 2.15.3
[ https://issues.apache.org/jira/browse/KAFKA-15208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA updated KAFKA-15208: --- Summary: Upgrade Jackson dependencies to version 2.15.3 (was: Upgrade Jackson dependencies to version 2.15.2) > Upgrade Jackson dependencies to version 2.15.3 > -- > > Key: KAFKA-15208 > URL: https://issues.apache.org/jira/browse/KAFKA-15208 > Project: Kafka > Issue Type: Improvement > Components: connect, kraft >Reporter: Said BOUDJELDA >Assignee: Said BOUDJELDA >Priority: Major > Labels: dependencies > Fix For: 3.7.0 > > > Upgrading the version of Jackson dependencies to the latest stable version > 2.15.2 can bring much bug fixing security issues solving and performance > improvement > > Check release notes back to the current version > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.15.2] > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14] > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KAFKA-15493) Ensure system tests work with Java 21
[
https://issues.apache.org/jira/browse/KAFKA-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770252#comment-17770252
]
Said BOUDJELDA commented on KAFKA-15493:
I need to redo all the test and start from O, I will compare between the old
and previous behaviour
> Ensure system tests work with Java 21
> -
>
> Key: KAFKA-15493
> URL: https://issues.apache.org/jira/browse/KAFKA-15493
> Project: Kafka
> Issue Type: Improvement
>Reporter: Ismael Juma
>Assignee: Said BOUDJELDA
>Priority: Major
> Fix For: 3.7.0
>
> Attachments: image-2023-09-28-02-11-49-196.png,
> image-2023-09-28-02-12-33-807.png
>
>
> Run the system tests as described below with Java 21:
> [https://github.com/apache/kafka/tree/trunk/tests]
> One relevant portion:
> Run tests with a different JVM (it may be as easy as replacing 11 with 21)
> {code:java}
> bash tests/docker/ducker-ak up -j 'openjdk:11';
> tests/docker/run_tests.sh{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (KAFKA-15493) Ensure system tests work with Java 21
[
https://issues.apache.org/jira/browse/KAFKA-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769856#comment-17769856
]
Said BOUDJELDA edited comment on KAFKA-15493 at 9/28/23 12:20 AM:
--
{code:java}
➜ kafka git:(trunk) java -version
openjdk version "21" 2023-09-19
OpenJDK Runtime Environment Homebrew (build 21)
OpenJDK 64-Bit Server VM Homebrew (build 21, mixed mode, sharing)
➜ kafka git:(trunk)
➜ kafka git:(trunk) ✗ bash tests/docker/run_tests.sh
WARNING: Ignoring custom format, because both --format and --quiet are set.
Starting a Gradle Daemon (subsequent builds will be faster)
> Configure project :
Starting build with version 3.7.0-SNAPSHOT (commit id 079e5d64) using Gradle
8.3, Java 21 and Scala 2.13.12
Build properties: maxParallelForks=12, maxScalacThreads=8, maxTestRetries=0
Deprecated Gradle features were used in this build, making it incompatible with
Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings
and determine if they come from your own scripts or plugins.
For more on this, please refer to
https://docs.gradle.org/8.3/userguide/command_line_interface.html#sec:command_line_warnings
in the Gradle documentation.
BUILD SUCCESSFUL in 9s {code}
I run tests with
ARG jdk_version=openjdk:21
FROM $jdk_version
was (Author: JIRAUSER301378):
{code:java}
➜ kafka git:(trunk) java -version
openjdk version "21" 2023-09-19
OpenJDK Runtime Environment Homebrew (build 21)
OpenJDK 64-Bit Server VM Homebrew (build 21, mixed mode, sharing)
➜ kafka git:(trunk)
➜ kafka git:(trunk) ✗ bash tests/docker/run_tests.sh
WARNING: Ignoring custom format, because both --format and --quiet are set.
Starting a Gradle Daemon (subsequent builds will be faster)
> Configure project :
Starting build with version 3.7.0-SNAPSHOT (commit id 079e5d64) using Gradle
8.3, Java 21 and Scala 2.13.12
Build properties: maxParallelForks=12, maxScalacThreads=8, maxTestRetries=0
Deprecated Gradle features were used in this build, making it incompatible with
Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings
and determine if they come from your own scripts or plugins.
For more on this, please refer to
https://docs.gradle.org/8.3/userguide/command_line_interface.html#sec:command_line_warnings
in the Gradle documentation.
BUILD SUCCESSFUL in 9s {code}
> Ensure system tests work with Java 21
> -
>
> Key: KAFKA-15493
> URL: https://issues.apache.org/jira/browse/KAFKA-15493
> Project: Kafka
> Issue Type: Improvement
>Reporter: Ismael Juma
>Assignee: Said BOUDJELDA
>Priority: Major
> Fix For: 3.7.0
>
> Attachments: image-2023-09-28-02-11-49-196.png,
> image-2023-09-28-02-12-33-807.png
>
>
> Run the system tests as described below with Java 21:
> [https://github.com/apache/kafka/tree/trunk/tests]
> One relevant portion:
> Run tests with a different JVM (it may be as easy as replacing 11 with 21)
> {code:java}
> bash tests/docker/ducker-ak up -j 'openjdk:11';
> tests/docker/run_tests.sh{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-15493) Ensure system tests work with Java 21
[
https://issues.apache.org/jira/browse/KAFKA-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769856#comment-17769856
]
Said BOUDJELDA commented on KAFKA-15493:
{code:java}
➜ kafka git:(trunk) java -version
openjdk version "21" 2023-09-19
OpenJDK Runtime Environment Homebrew (build 21)
OpenJDK 64-Bit Server VM Homebrew (build 21, mixed mode, sharing)
➜ kafka git:(trunk)
➜ kafka git:(trunk) ✗ bash tests/docker/run_tests.sh
WARNING: Ignoring custom format, because both --format and --quiet are set.
Starting a Gradle Daemon (subsequent builds will be faster)
> Configure project :
Starting build with version 3.7.0-SNAPSHOT (commit id 079e5d64) using Gradle
8.3, Java 21 and Scala 2.13.12
Build properties: maxParallelForks=12, maxScalacThreads=8, maxTestRetries=0
Deprecated Gradle features were used in this build, making it incompatible with
Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings
and determine if they come from your own scripts or plugins.
For more on this, please refer to
https://docs.gradle.org/8.3/userguide/command_line_interface.html#sec:command_line_warnings
in the Gradle documentation.
BUILD SUCCESSFUL in 9s {code}
> Ensure system tests work with Java 21
> -
>
> Key: KAFKA-15493
> URL: https://issues.apache.org/jira/browse/KAFKA-15493
> Project: Kafka
> Issue Type: Improvement
>Reporter: Ismael Juma
>Assignee: Said BOUDJELDA
>Priority: Major
> Fix For: 3.7.0
>
> Attachments: image-2023-09-28-02-11-49-196.png,
> image-2023-09-28-02-12-33-807.png
>
>
> Run the system tests as described below with Java 21:
> [https://github.com/apache/kafka/tree/trunk/tests]
> One relevant portion:
> Run tests with a different JVM (it may be as easy as replacing 11 with 21)
> {code:java}
> bash tests/docker/ducker-ak up -j 'openjdk:11';
> tests/docker/run_tests.sh{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (KAFKA-15493) Ensure system tests work with Java 21
[
https://issues.apache.org/jira/browse/KAFKA-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-15493:
---
Attachment: image-2023-09-28-02-12-33-807.png
> Ensure system tests work with Java 21
> -
>
> Key: KAFKA-15493
> URL: https://issues.apache.org/jira/browse/KAFKA-15493
> Project: Kafka
> Issue Type: Improvement
>Reporter: Ismael Juma
>Assignee: Said BOUDJELDA
>Priority: Major
> Fix For: 3.7.0
>
> Attachments: image-2023-09-28-02-11-49-196.png,
> image-2023-09-28-02-12-33-807.png
>
>
> Run the system tests as described below with Java 21:
> [https://github.com/apache/kafka/tree/trunk/tests]
> One relevant portion:
> Run tests with a different JVM (it may be as easy as replacing 11 with 21)
> {code:java}
> bash tests/docker/ducker-ak up -j 'openjdk:11';
> tests/docker/run_tests.sh{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (KAFKA-15493) Ensure system tests work with Java 21
[
https://issues.apache.org/jira/browse/KAFKA-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-15493:
---
Attachment: image-2023-09-28-02-11-49-196.png
> Ensure system tests work with Java 21
> -
>
> Key: KAFKA-15493
> URL: https://issues.apache.org/jira/browse/KAFKA-15493
> Project: Kafka
> Issue Type: Improvement
>Reporter: Ismael Juma
>Assignee: Said BOUDJELDA
>Priority: Major
> Fix For: 3.7.0
>
> Attachments: image-2023-09-28-02-11-49-196.png
>
>
> Run the system tests as described below with Java 21:
> [https://github.com/apache/kafka/tree/trunk/tests]
> One relevant portion:
> Run tests with a different JVM (it may be as easy as replacing 11 with 21)
> {code:java}
> bash tests/docker/ducker-ak up -j 'openjdk:11';
> tests/docker/run_tests.sh{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-15493) Ensure system tests work with Java 21
[
https://issues.apache.org/jira/browse/KAFKA-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769355#comment-17769355
]
Said BOUDJELDA commented on KAFKA-15493:
bash tests/docker/run_tests.sh passes with success
> Ensure system tests work with Java 21
> -
>
> Key: KAFKA-15493
> URL: https://issues.apache.org/jira/browse/KAFKA-15493
> Project: Kafka
> Issue Type: Improvement
>Reporter: Ismael Juma
>Assignee: Said BOUDJELDA
>Priority: Major
> Fix For: 3.7.0
>
>
> Run the system tests as described below with Java 21:
> [https://github.com/apache/kafka/tree/trunk/tests]
> One relevant portion:
> Run tests with a different JVM (it may be as easy as replacing 11 with 21)
> {code:java}
> bash tests/docker/ducker-ak up -j 'openjdk:11';
> tests/docker/run_tests.sh{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-15493) Ensure system tests work with Java 21
[
https://issues.apache.org/jira/browse/KAFKA-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769348#comment-17769348
]
Said BOUDJELDA commented on KAFKA-15493:
./gradlew clean systemTestLibs is passing with success
> Ensure system tests work with Java 21
> -
>
> Key: KAFKA-15493
> URL: https://issues.apache.org/jira/browse/KAFKA-15493
> Project: Kafka
> Issue Type: Improvement
>Reporter: Ismael Juma
>Assignee: Said BOUDJELDA
>Priority: Major
> Fix For: 3.7.0
>
>
> Run the system tests as described below with Java 21:
> [https://github.com/apache/kafka/tree/trunk/tests]
> One relevant portion:
> Run tests with a different JVM (it may be as easy as replacing 11 with 21)
> {code:java}
> bash tests/docker/ducker-ak up -j 'openjdk:11';
> tests/docker/run_tests.sh{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (KAFKA-15504) Upgrade snappy java to version 1.1.10.4
Said BOUDJELDA created KAFKA-15504: -- Summary: Upgrade snappy java to version 1.1.10.4 Key: KAFKA-15504 URL: https://issues.apache.org/jira/browse/KAFKA-15504 Project: Kafka Issue Type: Improvement Reporter: Said BOUDJELDA Assignee: Said BOUDJELDA The version 1.1.10.4 contains a fix of [CVE-2023-43642|https://github.com/xerial/snappy-java/security/advisories/GHSA-55g7-9cwv-5qfv] as mentioned on the release notes of the library [https://github.com/xerial/snappy-java/releases/tag/v1.1.10.4] Fixed SnappyInputStream so as not to allocate too large memory when decompressing data with an extremely large chunk size by -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KAFKA-15493) Ensure system tests work with Java 21
[
https://issues.apache.org/jira/browse/KAFKA-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768902#comment-17768902
]
Said BOUDJELDA commented on KAFKA-15493:
[~ijuma] I took your comment as a description of this ticket
> Ensure system tests work with Java 21
> -
>
> Key: KAFKA-15493
> URL: https://issues.apache.org/jira/browse/KAFKA-15493
> Project: Kafka
> Issue Type: Improvement
>Reporter: Ismael Juma
>Assignee: Said BOUDJELDA
>Priority: Major
> Fix For: 3.7.0
>
>
> Run the system tests as described below with Java 21:
> [https://github.com/apache/kafka/tree/trunk/tests]
> One relevant portion:
> Run tests with a different JVM (it may be as easy as replacing 11 with 21)
> {code:java}
> bash tests/docker/ducker-ak up -j 'openjdk:11';
> tests/docker/run_tests.sh{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (KAFKA-15493) Ensure system tests work with Java 21
[
https://issues.apache.org/jira/browse/KAFKA-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-15493:
---
Description:
Run the system tests as described below with Java 21:
[https://github.com/apache/kafka/tree/trunk/tests]
One relevant portion:
Run tests with a different JVM (it may be as easy as replacing 11 with 21)
{code:java}
bash tests/docker/ducker-ak up -j 'openjdk:11'; tests/docker/run_tests.sh{code}
> Ensure system tests work with Java 21
> -
>
> Key: KAFKA-15493
> URL: https://issues.apache.org/jira/browse/KAFKA-15493
> Project: Kafka
> Issue Type: Improvement
>Reporter: Ismael Juma
>Assignee: Said BOUDJELDA
>Priority: Major
> Fix For: 3.7.0
>
>
> Run the system tests as described below with Java 21:
> [https://github.com/apache/kafka/tree/trunk/tests]
> One relevant portion:
> Run tests with a different JVM (it may be as easy as replacing 11 with 21)
> {code:java}
> bash tests/docker/ducker-ak up -j 'openjdk:11';
> tests/docker/run_tests.sh{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-15496) Upgrade Jetty to version 11.0.16
[ https://issues.apache.org/jira/browse/KAFKA-15496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768606#comment-17768606 ] Said BOUDJELDA commented on KAFKA-15496: [~divijvaidya] Then this ticket can wait > Upgrade Jetty to version 11.0.16 > > > Key: KAFKA-15496 > URL: https://issues.apache.org/jira/browse/KAFKA-15496 > Project: Kafka > Issue Type: Improvement >Reporter: Said BOUDJELDA >Priority: Major > > Check release notes > [https://github.com/eclipse/jetty.project/releases/tag/jetty-11.0.16] > This task cannot be achieved without the upgrade of *jackson-databind* > library please check for more details KAFKA-15208 for more details > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KAFKA-15497) Refactor build.gradle and split each module configuration on the module itself
Said BOUDJELDA created KAFKA-15497: -- Summary: Refactor build.gradle and split each module configuration on the module itself Key: KAFKA-15497 URL: https://issues.apache.org/jira/browse/KAFKA-15497 Project: Kafka Issue Type: Improvement Reporter: Said BOUDJELDA The *build.gradle* file is getting too big and hard to maintain, a good reason to split this files over modules of the project, and let the root *build.gradle* file manage just the common parts of the projet, this will increase readability -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (KAFKA-15493) Ensure system tests work with Java 21
[ https://issues.apache.org/jira/browse/KAFKA-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA reassigned KAFKA-15493: -- Assignee: Said BOUDJELDA > Ensure system tests work with Java 21 > - > > Key: KAFKA-15493 > URL: https://issues.apache.org/jira/browse/KAFKA-15493 > Project: Kafka > Issue Type: Improvement >Reporter: Ismael Juma >Assignee: Said BOUDJELDA >Priority: Major > Fix For: 3.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (KAFKA-15485) Support building with Java 21 (LTS release)
[ https://issues.apache.org/jira/browse/KAFKA-15485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768454#comment-17768454 ] Said BOUDJELDA edited comment on KAFKA-15485 at 9/24/23 10:50 PM: -- [~ijuma] Can I take the KAFKA-15493 task then was (Author: JIRAUSER301378): [~ijuma] Can I take the KAFKA-15493 task then ? > Support building with Java 21 (LTS release) > --- > > Key: KAFKA-15485 > URL: https://issues.apache.org/jira/browse/KAFKA-15485 > Project: Kafka > Issue Type: Improvement >Reporter: Divij Vaidya >Assignee: Ismael Juma >Priority: Major > Fix For: 3.7.0 > > > JDK-21 is the latest LTS release which reached GA on 19th Sept 2023. This > ticket aims to upgrade JDK used by Kafka to JDK-21 (currently it's JDK20). > Thanks to proactive work done by [~ijuma] earlier [1][2][3], I do not > anticipate major hiccups while upgrading to JDK-21. > As part of this JIRA we want to: > 1. Upgrade Kafka to JDK 21 > 2. Replace the CI build for JDK 20 with JDK 21 (similar to [3] below) > 3. Update the README (see[4]) to mention Kafka's support for JDK-21 > [1] [https://github.com/apache/kafka/pull/13840] > [2] [https://github.com/apache/kafka/pull/13582] > [3] [https://github.com/apache/kafka/pull/12948] > [4] [https://github.com/apache/kafka/pull/14061] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (KAFKA-15485) Support building with Java 21 (LTS release)
[ https://issues.apache.org/jira/browse/KAFKA-15485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768454#comment-17768454 ] Said BOUDJELDA edited comment on KAFKA-15485 at 9/24/23 10:12 PM: -- [~ijuma] Can I take the KAFKA-15493 task then ? was (Author: JIRAUSER301378): [~ijuma] Can I take this task then ? > Support building with Java 21 (LTS release) > --- > > Key: KAFKA-15485 > URL: https://issues.apache.org/jira/browse/KAFKA-15485 > Project: Kafka > Issue Type: Improvement >Reporter: Divij Vaidya >Assignee: Ismael Juma >Priority: Major > Fix For: 3.7.0 > > > JDK-21 is the latest LTS release which reached GA on 19th Sept 2023. This > ticket aims to upgrade JDK used by Kafka to JDK-21 (currently it's JDK20). > Thanks to proactive work done by [~ijuma] earlier [1][2][3], I do not > anticipate major hiccups while upgrading to JDK-21. > As part of this JIRA we want to: > 1. Upgrade Kafka to JDK 21 > 2. Replace the CI build for JDK 20 with JDK 21 (similar to [3] below) > 3. Update the README (see[4]) to mention Kafka's support for JDK-21 > [1] [https://github.com/apache/kafka/pull/13840] > [2] [https://github.com/apache/kafka/pull/13582] > [3] [https://github.com/apache/kafka/pull/12948] > [4] [https://github.com/apache/kafka/pull/14061] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KAFKA-15485) Support building with Java 21 (LTS release)
[ https://issues.apache.org/jira/browse/KAFKA-15485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768454#comment-17768454 ] Said BOUDJELDA commented on KAFKA-15485: [~ijuma] Can I take this task then ? > Support building with Java 21 (LTS release) > --- > > Key: KAFKA-15485 > URL: https://issues.apache.org/jira/browse/KAFKA-15485 > Project: Kafka > Issue Type: Improvement >Reporter: Divij Vaidya >Assignee: Ismael Juma >Priority: Major > Fix For: 3.7.0 > > > JDK-21 is the latest LTS release which reached GA on 19th Sept 2023. This > ticket aims to upgrade JDK used by Kafka to JDK-21 (currently it's JDK20). > Thanks to proactive work done by [~ijuma] earlier [1][2][3], I do not > anticipate major hiccups while upgrading to JDK-21. > As part of this JIRA we want to: > 1. Upgrade Kafka to JDK 21 > 2. Replace the CI build for JDK 20 with JDK 21 (similar to [3] below) > 3. Update the README (see[4]) to mention Kafka's support for JDK-21 > [1] [https://github.com/apache/kafka/pull/13840] > [2] [https://github.com/apache/kafka/pull/13582] > [3] [https://github.com/apache/kafka/pull/12948] > [4] [https://github.com/apache/kafka/pull/14061] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KAFKA-15496) Upgrade Jetty to version 11.0.16
[ https://issues.apache.org/jira/browse/KAFKA-15496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768453#comment-17768453 ] Said BOUDJELDA commented on KAFKA-15496: [~divijvaidya] I want to know what do you think about this > Upgrade Jetty to version 11.0.16 > > > Key: KAFKA-15496 > URL: https://issues.apache.org/jira/browse/KAFKA-15496 > Project: Kafka > Issue Type: Improvement >Reporter: Said BOUDJELDA >Priority: Major > > Check release notes > [https://github.com/eclipse/jetty.project/releases/tag/jetty-11.0.16] > This task cannot be achieved without the upgrade of *jackson-databind* > library please check for more details KAFKA-15208 for more details > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KAFKA-15496) Upgrade Jetty to version 11.0.16
Said BOUDJELDA created KAFKA-15496: -- Summary: Upgrade Jetty to version 11.0.16 Key: KAFKA-15496 URL: https://issues.apache.org/jira/browse/KAFKA-15496 Project: Kafka Issue Type: Improvement Reporter: Said BOUDJELDA Check release notes [https://github.com/eclipse/jetty.project/releases/tag/jetty-11.0.16] This task cannot be achieved without the upgrade of *jackson-databind* library please check for more details KAFKA-15208 for more details -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KAFKA-15485) Support building with Java 21 (LTS release)
[ https://issues.apache.org/jira/browse/KAFKA-15485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768450#comment-17768450 ] Said BOUDJELDA commented on KAFKA-15485: [~ijuma] [~divijvaidya] do you have more details for the KAFKA-15493 I think I can give it a try > Support building with Java 21 (LTS release) > --- > > Key: KAFKA-15485 > URL: https://issues.apache.org/jira/browse/KAFKA-15485 > Project: Kafka > Issue Type: Improvement >Reporter: Divij Vaidya >Assignee: Ismael Juma >Priority: Major > Fix For: 3.7.0 > > > JDK-21 is the latest LTS release which reached GA on 19th Sept 2023. This > ticket aims to upgrade JDK used by Kafka to JDK-21 (currently it's JDK20). > Thanks to proactive work done by [~ijuma] earlier [1][2][3], I do not > anticipate major hiccups while upgrading to JDK-21. > As part of this JIRA we want to: > 1. Upgrade Kafka to JDK 21 > 2. Replace the CI build for JDK 20 with JDK 21 (similar to [3] below) > 3. Update the README (see[4]) to mention Kafka's support for JDK-21 > [1] [https://github.com/apache/kafka/pull/13840] > [2] [https://github.com/apache/kafka/pull/13582] > [3] [https://github.com/apache/kafka/pull/12948] > [4] [https://github.com/apache/kafka/pull/14061] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15494) Remove deprecated calls in build.gradle for preparing future upgrades
[
https://issues.apache.org/jira/browse/KAFKA-15494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-15494:
---
Description:
On the purpose of preparing the future upgrades of {*}Gradle wrapper{*}, we
need to get ride of the deprecated calls of certains methods as tasks
registrations, this will make the future upgrades to *Gradle 9* where plenty of
methods are marked for removal for this future big release, that will for sure
brings support for *JDK 21*
Running *Gradle* build with *--warning-mode all* reveals much warnings and much
deprecations for removal, and we have to be prepared from now to the future
changes
This is an example of deprecation warning
{code:java}
Build file '/Users/bmscomp/codes/kafka/build.gradle': line 3116
The org.gradle.api.plugins.Convention type has been deprecated. This is
scheduled to be removed in Gradle 9.0. Consult the upgrading guide for further
information:
https://docs.gradle.org/8.2.1/userguide/upgrading_version_8.html#deprecated_access_to_conventions
at
build_bpyr04xfzz0tpxxyqu97xn8xy$_run_closure58.doCall(/Users/bmscomp/codes/kafka/build.gradle:3116)
(Run with --stacktrace to get the full stack trace of this deprecation
warning.)
at
build_bpyr04xfzz0tpxxyqu97xn8xy.run(/Users/bmscomp/codes/kafka/build.gradle:3115)
(Run with --stacktrace to get the full stack trace of this deprecation
warning.) {code}
was:
On the purpose of preparing the future upgrades of {*}Gradle wrapper{*}, we
need to get ride of the deprecated calls of certains methods as tasks
registrations, this will make the future upgrades to *Gradle 9* where plenty of
methods are marked for removal for this future big release, that will for sure
brings support for *JDK 21*
Running *Gradle* build with *--warning-mode all* reveals much warnings and much
deprecations for removal, and we have to be prepared from now to the future
changes
> Remove deprecated calls in build.gradle for preparing future upgrades
> -
>
> Key: KAFKA-15494
> URL: https://issues.apache.org/jira/browse/KAFKA-15494
> Project: Kafka
> Issue Type: Improvement
>Reporter: Said BOUDJELDA
>Assignee: Said BOUDJELDA
>Priority: Major
>
> On the purpose of preparing the future upgrades of {*}Gradle wrapper{*}, we
> need to get ride of the deprecated calls of certains methods as tasks
> registrations, this will make the future upgrades to *Gradle 9* where plenty
> of methods are marked for removal for this future big release, that will for
> sure brings support for *JDK 21*
>
> Running *Gradle* build with *--warning-mode all* reveals much warnings and
> much deprecations for removal, and we have to be prepared from now to the
> future changes
>
>
> This is an example of deprecation warning
>
> {code:java}
> Build file '/Users/bmscomp/codes/kafka/build.gradle': line 3116
> The org.gradle.api.plugins.Convention type has been deprecated. This is
> scheduled to be removed in Gradle 9.0. Consult the upgrading guide for
> further information:
> https://docs.gradle.org/8.2.1/userguide/upgrading_version_8.html#deprecated_access_to_conventions
> at
> build_bpyr04xfzz0tpxxyqu97xn8xy$_run_closure58.doCall(/Users/bmscomp/codes/kafka/build.gradle:3116)
> (Run with --stacktrace to get the full stack trace of this
> deprecation warning.)
> at
> build_bpyr04xfzz0tpxxyqu97xn8xy.run(/Users/bmscomp/codes/kafka/build.gradle:3115)
> (Run with --stacktrace to get the full stack trace of this
> deprecation warning.) {code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (KAFKA-15494) Remove deprecated calls in build.gradle for preparing future upgrades
[
https://issues.apache.org/jira/browse/KAFKA-15494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-15494:
---
Description:
On the purpose of preparing the future upgrades of {*}Gradle wrapper{*}, we
need to get ride of the deprecated calls of certains methods as tasks
registrations, this will make the future upgrades to *Gradle 9* where plenty of
methods are marked for removal for this future big release, that will for sure
brings support for *JDK 21*
Running *Gradle* build with *--warning-mode all* reveals much warnings and much
deprecations for removal, and we have to be prepared from now to the future
changes
was:
On the purpose of preparing the future upgrades of Gradle wrapper, we need to
get ride of the deprecated calls of certains methods as tasks registrations,
this will make the future upgrades to *Gradle 9* where plenty of methods are
marked for removal for this future big release, that will for sure brings
support for *JDK 21*
For now trying to upgrade to Gradle 8.3 shows more deprecations then previous
version
> Remove deprecated calls in build.gradle for preparing future upgrades
> -
>
> Key: KAFKA-15494
> URL: https://issues.apache.org/jira/browse/KAFKA-15494
> Project: Kafka
> Issue Type: Improvement
>Reporter: Said BOUDJELDA
>Assignee: Said BOUDJELDA
>Priority: Major
>
> On the purpose of preparing the future upgrades of {*}Gradle wrapper{*}, we
> need to get ride of the deprecated calls of certains methods as tasks
> registrations, this will make the future upgrades to *Gradle 9* where plenty
> of methods are marked for removal for this future big release, that will for
> sure brings support for *JDK 21*
>
> Running *Gradle* build with *--warning-mode all* reveals much warnings and
> much deprecations for removal, and we have to be prepared from now to the
> future changes
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (KAFKA-15494) Remove deprecated calls in build.gradle for preparing future upgrades
[ https://issues.apache.org/jira/browse/KAFKA-15494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA updated KAFKA-15494: --- Summary: Remove deprecated calls in build.gradle for preparing future upgrades (was: Use tasks.register instead of task create in build.gradle) > Remove deprecated calls in build.gradle for preparing future upgrades > - > > Key: KAFKA-15494 > URL: https://issues.apache.org/jira/browse/KAFKA-15494 > Project: Kafka > Issue Type: Improvement >Reporter: Said BOUDJELDA >Assignee: Said BOUDJELDA >Priority: Major > > On the purpose of preparing the future upgrades of Gradle wrapper, we need to > get ride of the deprecated calls of certains methods as tasks registrations, > this will make the future upgrades to *Gradle 9* where plenty of methods are > marked for removal for this future big release, that will for sure brings > support for *JDK 21* > > For now trying to upgrade to Gradle 8.3 shows more deprecations then previous > version > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15494) Use tasks.register instead of task create in build.gradle
[ https://issues.apache.org/jira/browse/KAFKA-15494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA updated KAFKA-15494: --- Description: On the purpose of preparing the future upgrades of Gradle wrapper, we need to get ride of the deprecated calls of certains methods as tasks registrations, this will make the future upgrades to *Gradle 9* where plenty of methods are marked for removal for this future big release, that will for sure brings support for *JDK 21* For now trying to upgrade to Gradle 8.3 shows more deprecations then previous version was: On the purpose of preparing the future upgrades of Gradle wrapper, we need to get ride of the deprecated calls of certains methods as tasks registrations, this will make the future upgrades to *Gradle 9* where plenty of methods are marked for removal for this future big release, that will for sure brings support for *JDK 21* > Use tasks.register instead of task create in build.gradle > - > > Key: KAFKA-15494 > URL: https://issues.apache.org/jira/browse/KAFKA-15494 > Project: Kafka > Issue Type: Improvement >Reporter: Said BOUDJELDA >Assignee: Said BOUDJELDA >Priority: Major > > On the purpose of preparing the future upgrades of Gradle wrapper, we need to > get ride of the deprecated calls of certains methods as tasks registrations, > this will make the future upgrades to *Gradle 9* where plenty of methods are > marked for removal for this future big release, that will for sure brings > support for *JDK 21* > > For now trying to upgrade to Gradle 8.3 shows more deprecations then previous > version > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15494) Use tasks.register instead of task create in build.gradle
[ https://issues.apache.org/jira/browse/KAFKA-15494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA updated KAFKA-15494: --- Description: On the purpose of preparing the future upgrades of Gradle wrapper, we need to get ride of the deprecated calls of certains methods as tasks registrations, this will make the future upgrades to *Gradle 9* where plenty of methods are marked for removal for this future big release, that will for sure brings support for *JDK 21* For now trying to update was: On the purpose of preparing the future upgrades of Gradle wrapper, we need to get ride of the deprecated calls of certains methods as tasks registrations, this will make the future upgrades to *Gradle 9* where plenty of methods are marked for removal for this future big release, that will for sure brings support for *JDK 21* > Use tasks.register instead of task create in build.gradle > - > > Key: KAFKA-15494 > URL: https://issues.apache.org/jira/browse/KAFKA-15494 > Project: Kafka > Issue Type: Improvement >Reporter: Said BOUDJELDA >Assignee: Said BOUDJELDA >Priority: Major > > On the purpose of preparing the future upgrades of Gradle wrapper, we need to > get ride of the deprecated calls of certains methods as tasks registrations, > this will make the future upgrades to *Gradle 9* where plenty of methods are > marked for removal for this future big release, that will for sure brings > support for *JDK 21* > > For now trying to update > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15494) Use tasks.register instead of task create in build.gradle
[ https://issues.apache.org/jira/browse/KAFKA-15494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA updated KAFKA-15494: --- Description: On the purpose of preparing the future upgrades of Gradle wrapper, we need to get ride of the deprecated calls of certains methods as tasks registrations, this will make the future upgrades to *Gradle 9* where plenty of methods are marked for removal for this future big release, that will for sure brings support for *JDK 21* was: On the purpose of preparing the future upgrades of Gradle wrapper, we need to get ride of the deprecated calls of certains methods as tasks registrations, this will make the future upgrades to *Gradle 9* where plenty of methods are marked for removal for this future big release, that will for sure brings support for *JDK 21* For now trying to update > Use tasks.register instead of task create in build.gradle > - > > Key: KAFKA-15494 > URL: https://issues.apache.org/jira/browse/KAFKA-15494 > Project: Kafka > Issue Type: Improvement >Reporter: Said BOUDJELDA >Assignee: Said BOUDJELDA >Priority: Major > > On the purpose of preparing the future upgrades of Gradle wrapper, we need to > get ride of the deprecated calls of certains methods as tasks registrations, > this will make the future upgrades to *Gradle 9* where plenty of methods are > marked for removal for this future big release, that will for sure brings > support for *JDK 21* > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15494) Use tasks.register instead of task create in build.gradle
[ https://issues.apache.org/jira/browse/KAFKA-15494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA updated KAFKA-15494: --- Summary: Use tasks.register instead of task create in build.gradle (was: Remove deprecation call of task registration of Gradle on build.gradle and use tasks.register instead) > Use tasks.register instead of task create in build.gradle > - > > Key: KAFKA-15494 > URL: https://issues.apache.org/jira/browse/KAFKA-15494 > Project: Kafka > Issue Type: Improvement >Reporter: Said BOUDJELDA >Assignee: Said BOUDJELDA >Priority: Major > > On the purpose of preparing the future upgrades of Gradle wrapper, we need to > get ride of the deprecated calls of certains methods as tasks registrations, > this will make the future upgrades to *Gradle 9* where plenty of methods are > marked for removal for this future big release, that will for sure brings > support for *JDK 21* > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15494) Remove deprecation call of task registration of Gradle on build.gradle and use tasks.register instead
[
https://issues.apache.org/jira/browse/KAFKA-15494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-15494:
---
Description:
On the purpose of preparing the future upgrades of Gradle wrapper, we need to
get ride of the deprecated calls of certains methods as tasks registrations,
this will make the future upgrades to *Gradle 9* where plenty of methods are
marked for removal for this future big release, that will for sure brings
support for *JDK 21*
was:
On the purpose of preparing the future upgrades of Gradle wrapper, we need to
get ride of the deprecated calls of certains methods as tasks registrations,
this will make the future upgrades to *Gradle 9* where plenty of methods are
marked for removal for this future big release, that will for sure brings
support for *JDK 21*
an exemple of deprecated usage of task registration
{code:java}
task aggregatedJavadoc(type: Javadoc, dependsOn: compileJava) {
def projectsWithJavadoc = subprojects.findAll { it.javadoc.enabled }
source = projectsWithJavadoc.collect { it.sourceSets.main.allJava }
classpath = files(projectsWithJavadoc.collect {
it.sourceSets.main.compileClasspath })
includes = projectsWithJavadoc.collectMany { it.javadoc.getIncludes() }
excludes = projectsWithJavadoc.collectMany { it.javadoc.getExcludes() }
options.charSet = 'UTF-8'
options.docEncoding = 'UTF-8'
options.encoding = 'UTF-8'
// Turn off doclint for now, see
https://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html for
rationale
options.addStringOption('Xdoclint:none', '-quiet')
// The URL structure was changed to include the locale after Java 8
if (JavaVersion.current().isJava11Compatible())
options.links
"https://docs.oracle.com/en/java/javase/${JavaVersion.current().majorVersion}/docs/api/"
else
options.links "https://docs.oracle.com/javase/8/docs/api/;
}
{code}
> Remove deprecation call of task registration of Gradle on build.gradle and
> use tasks.register instead
> -
>
> Key: KAFKA-15494
> URL: https://issues.apache.org/jira/browse/KAFKA-15494
> Project: Kafka
> Issue Type: Improvement
>Reporter: Said BOUDJELDA
>Assignee: Said BOUDJELDA
>Priority: Major
>
> On the purpose of preparing the future upgrades of Gradle wrapper, we need to
> get ride of the deprecated calls of certains methods as tasks registrations,
> this will make the future upgrades to *Gradle 9* where plenty of methods are
> marked for removal for this future big release, that will for sure brings
> support for *JDK 21*
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (KAFKA-15494) Remove deprecation call of task registration of Gradle on build.gradle and use tasks.register instead
Said BOUDJELDA created KAFKA-15494:
--
Summary: Remove deprecation call of task registration of Gradle on
build.gradle and use tasks.register instead
Key: KAFKA-15494
URL: https://issues.apache.org/jira/browse/KAFKA-15494
Project: Kafka
Issue Type: Improvement
Reporter: Said BOUDJELDA
Assignee: Said BOUDJELDA
On the purpose of preparing the future upgrades of Gradle wrapper, we need to
get ride of the deprecated calls of certains methods as tasks registrations,
this will make the future upgrades to *Gradle 9* where plenty of methods are
marked for removal for this future big release, that will for sure brings
support for *JDK 21*
an exemple of deprecated usage of task registration
{code:java}
task aggregatedJavadoc(type: Javadoc, dependsOn: compileJava) {
def projectsWithJavadoc = subprojects.findAll { it.javadoc.enabled }
source = projectsWithJavadoc.collect { it.sourceSets.main.allJava }
classpath = files(projectsWithJavadoc.collect {
it.sourceSets.main.compileClasspath })
includes = projectsWithJavadoc.collectMany { it.javadoc.getIncludes() }
excludes = projectsWithJavadoc.collectMany { it.javadoc.getExcludes() }
options.charSet = 'UTF-8'
options.docEncoding = 'UTF-8'
options.encoding = 'UTF-8'
// Turn off doclint for now, see
https://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html for
rationale
options.addStringOption('Xdoclint:none', '-quiet')
// The URL structure was changed to include the locale after Java 8
if (JavaVersion.current().isJava11Compatible())
options.links
"https://docs.oracle.com/en/java/javase/${JavaVersion.current().majorVersion}/docs/api/"
else
options.links "https://docs.oracle.com/javase/8/docs/api/;
}
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17748189#comment-17748189
]
Said BOUDJELDA commented on KAFKA-15235:
[~ethaden] I do not think there is something wrong with your setup, can you
please give it one more try, and make sure you have pulled all recent changes
to your local machine and tell me the result please
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Assignee: Said BOUDJELDA
>Priority: Major
> Labels: buid, coverage, gradle, tools
> Fix For: 3.6.0, 3.5.2
>
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> ./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false{code}
>
> The error message states:
> {code:java}
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> {code}
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
>required = true
> }
> xml {
>required = true
> }
> csv{
> required = false
> }
> }
> }
> {code}
>
> However, even with these settings being accepted by Gradle, I was unable to
> generate any test coverage report. This might be due to some OOM issues, but
> I tried a lots of settings including increasing the maximum heap for the JVM
> gradle tasks without getting this to work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747217#comment-17747217
]
Said BOUDJELDA commented on KAFKA-15235:
[~ethaden] Please let me know more about your configuration, please check out
the branch I used to make a pull request to check the the behaviour of
generating jacoco html and xml reports
{code:java}
bmscomp:fix/jacaco_report_generation_issue
{code}
Please would you tell more more about your JDK version also I do not know if
this will help me really to produce that or not But really wish to get the same
setup as you
Thanks so much for your feedback
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Assignee: Said BOUDJELDA
>Priority: Major
> Labels: buid, coverage, gradle, tools
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> ./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false{code}
>
> The error message states:
> {code:java}
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> {code}
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
>required = true
> }
> xml {
>required = true
> }
> csv{
> required = false
> }
> }
> }
> {code}
>
> However, even with these settings being accepted by Gradle, I was unable to
> generate any test coverage report. This might be due to some OOM issues, but
> I tried a lots of settings including increasing the maximum heap for the JVM
> gradle tasks without getting this to work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (KAFKA-15097) NoSuchFileException in LogCleaner Operation.
[ https://issues.apache.org/jira/browse/KAFKA-15097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA reassigned KAFKA-15097: -- Assignee: Said BOUDJELDA > NoSuchFileException in LogCleaner Operation. > > > Key: KAFKA-15097 > URL: https://issues.apache.org/jira/browse/KAFKA-15097 > Project: Kafka > Issue Type: Bug > Components: log cleaner >Affects Versions: 3.3.1 >Reporter: Mukesh Mishra >Assignee: Said BOUDJELDA >Priority: Blocker > Attachments: __consumer_offset_49.png, config.txt, log-cleaner.log, > server.log > > > Currently we are facing NoSuchFileException in LogCleaner, which is critical > error as result platform get shutown. > We are running Kafka in Kraft Mode. > The cluster is having 3 Node. > Kafka version - 3.3.1 > We are facing issue systematically, which occurs after retention reached. > Here's the logs of Node 1 for consumer offset 4146 for which we have faced > NoSuchFileException on 24 may 2023 > Config : > [^config.txt] > ^Logs :^ > ^Server Node 1 [^server.log]^ > Log Cleaner : > [^log-cleaner.log] > ^__consumer_offset_49 directory logs :^ > ^!__consumer_offset_49.png!^ > we suspect that swap operation is culprit as we can see swap file for > consumer offset 4146 for __consumer_offset_49 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KAFKA-15097) NoSuchFileException in LogCleaner Operation.
[ https://issues.apache.org/jira/browse/KAFKA-15097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747212#comment-17747212 ] Said BOUDJELDA commented on KAFKA-15097: I really want to take this ticket and start first by reproducing the issue, [~mksmsr] I'll of course need your to at least reproduce this bug > NoSuchFileException in LogCleaner Operation. > > > Key: KAFKA-15097 > URL: https://issues.apache.org/jira/browse/KAFKA-15097 > Project: Kafka > Issue Type: Bug > Components: log cleaner >Affects Versions: 3.3.1 >Reporter: Mukesh Mishra >Priority: Blocker > Attachments: __consumer_offset_49.png, config.txt, log-cleaner.log, > server.log > > > Currently we are facing NoSuchFileException in LogCleaner, which is critical > error as result platform get shutown. > We are running Kafka in Kraft Mode. > The cluster is having 3 Node. > Kafka version - 3.3.1 > We are facing issue systematically, which occurs after retention reached. > Here's the logs of Node 1 for consumer offset 4146 for which we have faced > NoSuchFileException on 24 may 2023 > Config : > [^config.txt] > ^Logs :^ > ^Server Node 1 [^server.log]^ > Log Cleaner : > [^log-cleaner.log] > ^__consumer_offset_49 directory logs :^ > ^!__consumer_offset_49.png!^ > we suspect that swap operation is culprit as we can see swap file for > consumer offset 4146 for __consumer_offset_49 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KAFKA-14969) Upgrade Mockito to 4.11.0
[
https://issues.apache.org/jira/browse/KAFKA-14969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746830#comment-17746830
]
Said BOUDJELDA commented on KAFKA-14969:
Thank you [~ijuma] I just saw the comments in the code
{code:java}
// We use Mockito 4.11 with Scala 2.13+ for Java 20 support and Mockito 4.9
with Scala 2.12
// to workaround ambiguous reference to `Mockito.spy` compiler errors. Since
Scala 2.12 support
// is going away soon, this is simpler than adjusting the code.
String mockitoVersion
if (scalaVersion == "2.12")
mockitoVersion = "4.9.0"
else
mockitoVersion = "4.11.0"{code}
> Upgrade Mockito to 4.11.0
> -
>
> Key: KAFKA-14969
> URL: https://issues.apache.org/jira/browse/KAFKA-14969
> Project: Kafka
> Issue Type: Improvement
> Components: unit tests
>Reporter: Divij Vaidya
>Priority: Minor
> Labels: dependencies
> Fix For: 3.6.0
>
>
> Upgrading to Mockito 4.11.0 leads to following errors. Need to fix them
> before upgrade. Note that we cannot upgrade to Mockito 5 because it doesn't
> support JDK 8.
> {code:java}
> [2023-05-05T12:21:58.628Z] > Task :core:compileTestScala
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2654:31:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types
> (kafka.server.metadata.MockConfigRepository)
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2658:25:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types (kafka.log.LogManager)
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2688:31:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types
> (kafka.server.metadata.MockConfigRepository)
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2692:25:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types (kafka.log.LogManager)
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2728:31:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types
> (kafka.server.metadata.MockConfigRepository)
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2734:25:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types (kafka.log.LogManager)
> [2023-05-05T12:22:06.267Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/controller/ControllerIntegrationTest.scala:807:21:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:22:06.267Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:22:06.267Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:22:06.267Z] match argument types
> (controller.eventManager.ControllerEventThread)
> [2023-05-05T12:22:06.267Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/controller/ControllerIntegrationTest.scala:838:21:
> ambiguous reference to overloaded
[jira] [Commented] (KAFKA-14969) Upgrade Mockito to 4.11.0
[
https://issues.apache.org/jira/browse/KAFKA-14969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746667#comment-17746667
]
Said BOUDJELDA commented on KAFKA-14969:
Can I take this ticket, and prepare even the most recent Mockito versions
upgrades
> Upgrade Mockito to 4.11.0
> -
>
> Key: KAFKA-14969
> URL: https://issues.apache.org/jira/browse/KAFKA-14969
> Project: Kafka
> Issue Type: Improvement
> Components: unit tests
>Reporter: Divij Vaidya
>Priority: Minor
> Labels: dependencies
> Fix For: 3.6.0
>
>
> Upgrading to Mockito 4.11.0 leads to following errors. Need to fix them
> before upgrade. Note that we cannot upgrade to Mockito 5 because it doesn't
> support JDK 8.
> {code:java}
> [2023-05-05T12:21:58.628Z] > Task :core:compileTestScala
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2654:31:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types
> (kafka.server.metadata.MockConfigRepository)
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2658:25:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types (kafka.log.LogManager)
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2688:31:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types
> (kafka.server.metadata.MockConfigRepository)
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2692:25:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types (kafka.log.LogManager)
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2728:31:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types
> (kafka.server.metadata.MockConfigRepository)
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2734:25:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types (kafka.log.LogManager)
> [2023-05-05T12:22:06.267Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/controller/ControllerIntegrationTest.scala:807:21:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:22:06.267Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:22:06.267Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:22:06.267Z] match argument types
> (controller.eventManager.ControllerEventThread)
> [2023-05-05T12:22:06.267Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/controller/ControllerIntegrationTest.scala:838:21:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:22:06.267Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:22:06.267Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:22:06.267Z] match argument types
> (controller.eventManager.ControllerEventThread){code}
> {code:java}
> [2023-05-05T12:22:40.865Z] > Task
[jira] [Updated] (KAFKA-14969) Upgrade Mockito to 4.11.0
[
https://issues.apache.org/jira/browse/KAFKA-14969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-14969:
---
Labels: dependencies (was: )
> Upgrade Mockito to 4.11.0
> -
>
> Key: KAFKA-14969
> URL: https://issues.apache.org/jira/browse/KAFKA-14969
> Project: Kafka
> Issue Type: Improvement
> Components: unit tests
>Reporter: Divij Vaidya
>Priority: Minor
> Labels: dependencies
> Fix For: 3.6.0
>
>
> Upgrading to Mockito 4.11.0 leads to following errors. Need to fix them
> before upgrade. Note that we cannot upgrade to Mockito 5 because it doesn't
> support JDK 8.
> {code:java}
> [2023-05-05T12:21:58.628Z] > Task :core:compileTestScala
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2654:31:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types
> (kafka.server.metadata.MockConfigRepository)
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2658:25:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types (kafka.log.LogManager)
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2688:31:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types
> (kafka.server.metadata.MockConfigRepository)
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2692:25:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types (kafka.log.LogManager)
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2728:31:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types
> (kafka.server.metadata.MockConfigRepository)
> [2023-05-05T12:21:58.628Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/cluster/PartitionTest.scala:2734:25:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:21:58.628Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:21:58.628Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:21:58.628Z] match argument types (kafka.log.LogManager)
> [2023-05-05T12:22:06.267Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/controller/ControllerIntegrationTest.scala:807:21:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:22:06.267Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:22:06.267Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:22:06.267Z] match argument types
> (controller.eventManager.ControllerEventThread)
> [2023-05-05T12:22:06.267Z] [Error]
> /home/jenkins/jenkins-agent/712657a4/workspace/Kafka_kafka-pr_PR-13673/core/src/test/scala/unit/kafka/controller/ControllerIntegrationTest.scala:838:21:
> ambiguous reference to overloaded definition,
> [2023-05-05T12:22:06.267Z] both method spy in class Mockito of type [T](x$1:
> T*)T
> [2023-05-05T12:22:06.267Z] and method spy in class Mockito of type [T](x$1:
> T)T
> [2023-05-05T12:22:06.267Z] match argument types
> (controller.eventManager.ControllerEventThread){code}
> {code:java}
> [2023-05-05T12:22:40.865Z] > Task :core:compileTestScala
> [2023-05-05T12:22:40.865Z] [Error]
>
[jira] [Updated] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-15235:
---
Description:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running
{code:java}
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false{code}
The error message states:
{code:java}
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
{code}
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
{code}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true
}
csv{
required = false
}
}
}
{code}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
was:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running
{code:java}
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false{code}
The error message states:
{code:java}
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
{code}
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
{code}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true
}
csv{
required = false
}
}
}
{code}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Assignee: Said BOUDJELDA
>Priority: Major
> Labels: buid, coverage, gradle, tools
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> ./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false{code}
>
> The error message states:
> {code:java}
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> {code}
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
>
[jira] [Comment Edited] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746387#comment-17746387
]
Said BOUDJELDA edited comment on KAFKA-15235 at 7/24/23 10:48 AM:
--
[~ethaden] For the pull request I made, and for this command
{code:java}
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false{code}
the path to the generated html report :
{code:java}
kafka/clients/build/reports/jacoco/test/html/index.html{code}
and the xml report :
{code:java}
kafka/clients/build/reports/jacoco/test/jacocoTestReport.xml {code}
was (Author: JIRAUSER301378):
[~ethaden] For the pull request I made, and for this command
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false
the path to the generated html report :
{code:java}
kafka/clients/build/reports/jacoco/test/html/index.html{code}
and the xml report :
{code:java}
kafka/clients/build/reports/jacoco/test/jacocoTestReport.xml {code}
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Assignee: Said BOUDJELDA
>Priority: Major
> Labels: buid, coverage, gradle, tools
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> ./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false{code}
>
> The error message states:
> {code:java}
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
> {code}
>
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
>required = true
> }
> xml {
>required = true
> }
> csv{
> required = false
> }
> }
> }
> {code}
>
> However, even with these settings being accepted by Gradle, I was unable to
> generate any test coverage report. This might be due to some OOM issues, but
> I tried a lots of settings including increasing the maximum heap for the JVM
> gradle tasks without getting this to work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746387#comment-17746387
]
Said BOUDJELDA edited comment on KAFKA-15235 at 7/24/23 10:47 AM:
--
[~ethaden] For the pull request I made, and for this command
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false
the path to the generated html report
{code:java}
kafka/clients/build/reports/jacoco/test/html/index.html{code}
and the xml report :
{code:java}
kafka/clients/build/reports/jacoco/test/jacocoTestReport.xml {code}
was (Author: JIRAUSER301378):
[~ethaden] For the pull request I made, and for this command
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false
the path to the generated html report
{code:java}
kafka/clients/build/reports/jacoco/test/html/index.html{code}
and the xml report :
{code:java}
kafka/clients/build/reports/jacoco/test/jacocoTestReport.xml {code}
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Assignee: Said BOUDJELDA
>Priority: Major
> Labels: buid, coverage, gradle, tools
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> ./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false{code}
>
> The error message states:
> {code:java}
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
> {code}
>
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
>required = true
> }
> xml {
>required = true
> }
> csv{
> required = false
> }
> }
> }
> {code}
>
> However, even with these settings being accepted by Gradle, I was unable to
> generate any test coverage report. This might be due to some OOM issues, but
> I tried a lots of settings including increasing the maximum heap for the JVM
> gradle tasks without getting this to work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746387#comment-17746387
]
Said BOUDJELDA edited comment on KAFKA-15235 at 7/24/23 10:47 AM:
--
[~ethaden] For the pull request I made, and for this command
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false
the path to the generated html report :
{code:java}
kafka/clients/build/reports/jacoco/test/html/index.html{code}
and the xml report :
{code:java}
kafka/clients/build/reports/jacoco/test/jacocoTestReport.xml {code}
was (Author: JIRAUSER301378):
[~ethaden] For the pull request I made, and for this command
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false
the path to the generated html report
{code:java}
kafka/clients/build/reports/jacoco/test/html/index.html{code}
and the xml report :
{code:java}
kafka/clients/build/reports/jacoco/test/jacocoTestReport.xml {code}
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Assignee: Said BOUDJELDA
>Priority: Major
> Labels: buid, coverage, gradle, tools
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> ./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false{code}
>
> The error message states:
> {code:java}
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
> {code}
>
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
>required = true
> }
> xml {
>required = true
> }
> csv{
> required = false
> }
> }
> }
> {code}
>
> However, even with these settings being accepted by Gradle, I was unable to
> generate any test coverage report. This might be due to some OOM issues, but
> I tried a lots of settings including increasing the maximum heap for the JVM
> gradle tasks without getting this to work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746387#comment-17746387
]
Said BOUDJELDA commented on KAFKA-15235:
[~ethaden] For the pull request I made, and for this command
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false
the path to the generated html report
{code:java}
kafka/clients/build/reports/jacoco/test/html/index.html{code}
and the xml report :
{code:java}
kafka/clients/build/reports/jacoco/test/jacocoTestReport.xml {code}
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Assignee: Said BOUDJELDA
>Priority: Major
> Labels: buid, coverage, gradle, tools
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> ./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false{code}
>
> The error message states:
> {code:java}
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
> {code}
>
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
>required = true
> }
> xml {
>required = true
> }
> csv{
> required = false
> }
> }
> }
> {code}
>
> However, even with these settings being accepted by Gradle, I was unable to
> generate any test coverage report. This might be due to some OOM issues, but
> I tried a lots of settings including increasing the maximum heap for the JVM
> gradle tasks without getting this to work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745996#comment-17745996
]
Said BOUDJELDA commented on KAFKA-15235:
[~ethaden] I already made a pull request that tried to fix this issue, it's
generating a report in a local build and we need to check the behaviour of
Jenkins build before merging. I invite you and folks to review this PR and
check build
Linke to pull request : [https://github.com/apache/kafka/pull/14075]
Thanks
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Assignee: Said BOUDJELDA
>Priority: Major
> Labels: buid, coverage, gradle, tools
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> ./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false{code}
>
> The error message states:
> {code:java}
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
> {code}
>
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
>required = true
> }
> xml {
>required = true
> }
> csv{
> required = false
> }
> }
> }
> {code}
>
> However, even with these settings being accepted by Gradle, I was unable to
> generate any test coverage report. This might be due to some OOM issues, but
> I tried a lots of settings including increasing the maximum heap for the JVM
> gradle tasks without getting this to work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-15235:
---
Description:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running
{code:java}
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false{code}
The error message states:
{code:java}
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
{code}
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
{code}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true
}
csv{
required = false
}
}
}
{code}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
was:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running
{code:java}
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false{code}
The error message states:
{code:java}
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
{code}
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
{code}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true
}
csv{
required = false
}
}
}
{code}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Assignee: Said BOUDJELDA
>Priority: Major
> Labels: buid, coverage, gradle, tools
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> ./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false{code}
>
> The error message states:
> {code:java}
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
> {code}
>
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
>
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
>
[jira] [Updated] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-15235:
---
Description:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running
{code:java}
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false{code}
The error message states:
{code:java}
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
{code}
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
{code}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true
}
csv{
required = false
}
}
}
{code}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
was:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running
{code:java}
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false{code}
The error message states:
{code:java}
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
{code}
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
{code}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true
}
csv{
required = false
}
}
}
{code}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Assignee: Said BOUDJELDA
>Priority: Major
> Labels: buid, coverage, gradle, tools
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> ./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false{code}
>
> The error message states:
> {code:java}
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
> {code}
>
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets
[jira] [Updated] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-15235:
---
Description:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running
{code:java}
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false{code}
The error message states:
{code:java}
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
{code}
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
{code}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true
}
csv{
required = false
}
}
}
{code}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
was:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running
{code:java}
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false{code}
The error message states:
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
{code}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true
}
csv{
required = false
}
}
}
{code}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Assignee: Said BOUDJELDA
>Priority: Major
> Labels: buid, coverage, gradle, tools
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> ./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false{code}
> The error message states:
>
> {code:java}
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
> {code}
>
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
>
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
[jira] [Updated] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-15235:
---
Labels: buid coverage gradle tools (was: )
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Assignee: Said BOUDJELDA
>Priority: Major
> Labels: buid, coverage, gradle, tools
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> ./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false{code}
> The error message states:
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
>
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
>required = true
> }
> xml {
>required = true
> }
> csv{
> required = false
> }
> }
> }
> {code}
>
> However, even with these settings being accepted by Gradle, I was unable to
> generate any test coverage report. This might be due to some OOM issues, but
> I tried a lots of settings including increasing the maximum heap for the JVM
> gradle tasks without getting this to work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745995#comment-17745995
]
Said BOUDJELDA commented on KAFKA-15235:
I think I have a solution for this, I'll take this Jira
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Priority: Major
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> ./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false{code}
> The error message states:
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
>
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
>required = true
> }
> xml {
>required = true
> }
> csv{
> required = false
> }
> }
> }
> {code}
>
> However, even with these settings being accepted by Gradle, I was unable to
> generate any test coverage report. This might be due to some OOM issues, but
> I tried a lots of settings including increasing the maximum heap for the JVM
> gradle tasks without getting this to work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA reassigned KAFKA-15235:
--
Assignee: Said BOUDJELDA
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Assignee: Said BOUDJELDA
>Priority: Major
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> ./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false{code}
> The error message states:
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
>
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
>required = true
> }
> xml {
>required = true
> }
> csv{
> required = false
> }
> }
> }
> {code}
>
> However, even with these settings being accepted by Gradle, I was unable to
> generate any test coverage report. This might be due to some OOM issues, but
> I tried a lots of settings including increasing the maximum heap for the JVM
> gradle tasks without getting this to work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-15235:
---
Description:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running
{code:java}
./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false{code}
The error message states:
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
{code}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true
}
csv{
required = false
}
}
}
{code}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
was:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running
{code:java}
"./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false". {code}
The error message states:
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
{code}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true
}
csv{
required = false
}
}
}
{code}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Priority: Major
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> ./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false{code}
> The error message states:
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
>
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
>required = true
> }
> xml {
>required = true
> }
[jira] [Updated] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-15235:
---
Description:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running
{code:java}
"./gradlew clients:reportCoverage -PenableTestCoverage=true
-Dorg.gradle.parallel=false". {code}
The error message states:
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
{code}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true
}
csv{
required = false
}
}
}
{code}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
was:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running "./gradlew
clients:reportCoverage -PenableTestCoverage=true -Dorg.gradle.parallel=false".
The error message states:
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
{code}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true
}
csv{
required = false
}
}
}
{code}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Priority: Major
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running
> {code:java}
> "./gradlew clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false". {code}
> The error message states:
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
>
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
>required = true
> }
> xml {
>required = true
> }
>
[jira] [Updated] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-15235:
---
Description:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running "./gradlew
clients:reportCoverage -PenableTestCoverage=true -Dorg.gradle.parallel=false".
The error message states:
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
{code}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true
}
csv{
required = false
}
}
}
{code}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
was:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running "./gradlew
clients:reportCoverage -PenableTestCoverage=true -Dorg.gradle.parallel=false".
The error message states:
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
{code}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true }
csv{
required = false
}
}
}
{code}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Priority: Major
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running "./gradlew
> clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false". The error message states:
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
>
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
>required = true
> }
> xml {
>required = true
> }
> csv{
> required = false
> }
>
[jira] [Updated] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Said BOUDJELDA updated KAFKA-15235:
---
Description:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running "./gradlew
clients:reportCoverage -PenableTestCoverage=true -Dorg.gradle.parallel=false".
The error message states:
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
{code}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
{code:java}
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true }
csv{
required = false
}
}
}
{code}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
was:
On current dev branch, gradle 8.x fails while trying to generate test coverage
reports as stated in the README, e.g. by running "./gradlew
clients:reportCoverage -PenableTestCoverage=true -Dorg.gradle.parallel=false".
The error message states:
"Could not set unknown property 'enabled' for Report html of type
org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
In "build.gradle", the library "jacoco" which is used to generate test coverage
reports for the Java code is configured in two different places with these
settings:
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html.enabled = true
xml.enabled = true
csv.enabled = false
}
}
With the latest version of jacoco, shipped with gradle 8.x, these config
options are not compatible anymore. A correct configuration might look like
like this:
jacocoTestReport {
dependsOn tasks.test
sourceSets sourceSets.main
reports {
html {
required = true
}
xml {
required = true
}
csv {
required = false
}
}
}
However, even with these settings being accepted by Gradle, I was unable to
generate any test coverage report. This might be due to some OOM issues, but I
tried a lots of settings including increasing the maximum heap for the JVM
gradle tasks without getting this to work.
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Priority: Major
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running "./gradlew
> clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false". The error message states:
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> {code}
>
>
>
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
>
> {code:java}
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
>required = true
> }
> xml {
>required = true }
> csv{
> required = false
> }
> }
> }
> {code}
>
> However, even with these settings being accepted by Gradle, I
[jira] [Comment Edited] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745985#comment-17745985
]
Said BOUDJELDA edited comment on KAFKA-15235 at 7/22/23 8:03 PM:
-
[~ethaden] I can give this a try if you want , can I assigne the Jira ticket
to me please
was (Author: JIRAUSER301378):
[~ethaden] I can give this a try if you want ?
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Priority: Major
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running "./gradlew
> clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false". The error message states:
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
> required = true
> }
> xml {
> required = true
> }
> csv {
> required = false
> }
> }
> }
> However, even with these settings being accepted by Gradle, I was unable to
> generate any test coverage report. This might be due to some OOM issues, but
> I tried a lots of settings including increasing the maximum heap for the JVM
> gradle tasks without getting this to work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745985#comment-17745985
]
Said BOUDJELDA edited comment on KAFKA-15235 at 7/22/23 8:03 PM:
-
[~ethaden] I can give this a try if you want ?
was (Author: JIRAUSER301378):
I can give this a try if you want ?
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Priority: Major
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running "./gradlew
> clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false". The error message states:
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
> required = true
> }
> xml {
> required = true
> }
> csv {
> required = false
> }
> }
> }
> However, even with these settings being accepted by Gradle, I was unable to
> generate any test coverage report. This might be due to some OOM issues, but
> I tried a lots of settings including increasing the maximum heap for the JVM
> gradle tasks without getting this to work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-15235) No test coverage reports for Java due to settings for Jacoco being incompatible with Gradle 8.x
[
https://issues.apache.org/jira/browse/KAFKA-15235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745985#comment-17745985
]
Said BOUDJELDA commented on KAFKA-15235:
I can give this a try if you want ?
> No test coverage reports for Java due to settings for Jacoco being
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
> Issue Type: Bug
> Components: unit tests
>Affects Versions: 3.6.0
>Reporter: Eike Thaden
>Priority: Major
>
> On current dev branch, gradle 8.x fails while trying to generate test
> coverage reports as stated in the README, e.g. by running "./gradlew
> clients:reportCoverage -PenableTestCoverage=true
> -Dorg.gradle.parallel=false". The error message states:
> "Could not set unknown property 'enabled' for Report html of type
> org.gradle.api.reporting.internal.TaskGeneratedSingleDirectoryReport"
> In "build.gradle", the library "jacoco" which is used to generate test
> coverage reports for the Java code is configured in two different places with
> these settings:
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html.enabled = true
> xml.enabled = true
> csv.enabled = false
> }
> }
> With the latest version of jacoco, shipped with gradle 8.x, these config
> options are not compatible anymore. A correct configuration might look like
> like this:
> jacocoTestReport {
> dependsOn tasks.test
> sourceSets sourceSets.main
> reports {
> html {
> required = true
> }
> xml {
> required = true
> }
> csv {
> required = false
> }
> }
> }
> However, even with these settings being accepted by Gradle, I was unable to
> generate any test coverage report. This might be due to some OOM issues, but
> I tried a lots of settings including increasing the maximum heap for the JVM
> gradle tasks without getting this to work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (KAFKA-1718) "Message Size Too Large" error when only small messages produced with Snappy
[ https://issues.apache.org/jira/browse/KAFKA-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745983#comment-17745983 ] Said BOUDJELDA commented on KAFKA-1718: --- Does this bug exists always ? > "Message Size Too Large" error when only small messages produced with Snappy > > > Key: KAFKA-1718 > URL: https://issues.apache.org/jira/browse/KAFKA-1718 > Project: Kafka > Issue Type: Bug > Components: core >Affects Versions: 0.8.1.1 >Reporter: Evan Huus >Priority: Critical > > I'm the primary author of the Go bindings, and while I originally received > this as a bug against my bindings, I'm coming to the conclusion that it's a > bug in the broker somehow. > Specifically, take a look at the last two kafka packets in the following > packet capture: https://dl.dropboxusercontent.com/u/171647/kafka.pcapng (you > will need a trunk build of Wireshark to fully decode the kafka part of the > packets). > The produce request contains two partitions on one topic. Each partition has > one message set (sizes 977205 bytes and 967362 bytes respectively). Each > message set is a sequential collection of snappy-compressed messages, each > message of size 46899. When uncompressed, each message contains a message set > of 999600 bytes, containing a sequence of uncompressed 1024-byte messages. > However, the broker responds to this with a MessageSizeTooLarge error, full > stacktrace from the broker logs being: > kafka.common.MessageSizeTooLargeException: Message size is 1070127 bytes > which exceeds the maximum configured message size of 112. > at kafka.log.Log$$anonfun$append$1.apply(Log.scala:267) > at kafka.log.Log$$anonfun$append$1.apply(Log.scala:265) > at scala.collection.Iterator$class.foreach(Iterator.scala:727) > at kafka.utils.IteratorTemplate.foreach(IteratorTemplate.scala:32) > at kafka.log.Log.append(Log.scala:265) > at kafka.cluster.Partition.appendMessagesToLeader(Partition.scala:354) > at > kafka.server.KafkaApis$$anonfun$appendToLocalLog$2.apply(KafkaApis.scala:376) > at > kafka.server.KafkaApis$$anonfun$appendToLocalLog$2.apply(KafkaApis.scala:366) > at > scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244) > at > scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244) > at > scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:98) > at > scala.collection.mutable.HashMap$$anonfun$foreach$1.apply(HashMap.scala:98) > at > scala.collection.mutable.HashTable$class.foreachEntry(HashTable.scala:226) > at scala.collection.mutable.HashMap.foreachEntry(HashMap.scala:39) > at scala.collection.mutable.HashMap.foreach(HashMap.scala:98) > at scala.collection.TraversableLike$class.map(TraversableLike.scala:244) > at scala.collection.AbstractTraversable.map(Traversable.scala:105) > at kafka.server.KafkaApis.appendToLocalLog(KafkaApis.scala:366) > at kafka.server.KafkaApis.handleProducerRequest(KafkaApis.scala:292) > at kafka.server.KafkaApis.handle(KafkaApis.scala:185) > at kafka.server.KafkaRequestHandler.run(KafkaRequestHandler.scala:42) > at java.lang.Thread.run(Thread.java:695) > Since as far as I can tell none of the sizes in the actual produced packet > exceed the defined maximum, I can only assume that the broker is > miscalculating something somewhere and throwing the exception improperly. > --- > This issue can be reliably reproduced using an out-of-the-box binary download > of 0.8.1.1 and the following gist: > https://gist.github.com/eapache/ce0f15311c605a165ce7 (you will need to use > the `producer-ng` branch of the Sarama library). > --- > I am happy to provide any more information you might need, or to do relevant > experiments etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (KAFKA-15217) Consider usage of Gradle toolchain to specify Java version
[ https://issues.apache.org/jira/browse/KAFKA-15217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745507#comment-17745507 ] Said BOUDJELDA edited comment on KAFKA-15217 at 7/21/23 2:28 PM: - [~divijvaidya] Thank you, I'll assigned the Jira fto me was (Author: JIRAUSER301378): [~divijvaidya] Thank you, I'll assigned the Jira for me > Consider usage of Gradle toolchain to specify Java version > -- > > Key: KAFKA-15217 > URL: https://issues.apache.org/jira/browse/KAFKA-15217 > Project: Kafka > Issue Type: Improvement >Reporter: Divij Vaidya >Assignee: Said BOUDJELDA >Priority: Minor > > We recently started using Gradle 8.2. It has a new feature called toolchains > [1] which could be used in our project. This task is to explore that feature > consider it's usage for Kafka. > [1] https://docs.gradle.org/8.2/userguide/toolchains.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (KAFKA-15217) Consider usage of Gradle toolchain to specify Java version
[ https://issues.apache.org/jira/browse/KAFKA-15217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745507#comment-17745507 ] Said BOUDJELDA edited comment on KAFKA-15217 at 7/21/23 9:24 AM: - [~divijvaidya] Thank you, I'll assigned the Jira for me was (Author: JIRAUSER301378): [~divijvaidya] Thank you, I assigned the Jira for me > Consider usage of Gradle toolchain to specify Java version > -- > > Key: KAFKA-15217 > URL: https://issues.apache.org/jira/browse/KAFKA-15217 > Project: Kafka > Issue Type: Improvement >Reporter: Divij Vaidya >Assignee: Said BOUDJELDA >Priority: Minor > > We recently started using Gradle 8.2. It has a new feature called toolchains > [1] which could be used in our project. This task is to explore that feature > consider it's usage for Kafka. > [1] https://docs.gradle.org/8.2/userguide/toolchains.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KAFKA-15217) Consider usage of Gradle toolchain to specify Java version
[ https://issues.apache.org/jira/browse/KAFKA-15217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745507#comment-17745507 ] Said BOUDJELDA commented on KAFKA-15217: [~divijvaidya] Thank you, I assigned the Jira for me > Consider usage of Gradle toolchain to specify Java version > -- > > Key: KAFKA-15217 > URL: https://issues.apache.org/jira/browse/KAFKA-15217 > Project: Kafka > Issue Type: Improvement >Reporter: Divij Vaidya >Assignee: Said BOUDJELDA >Priority: Minor > > We recently started using Gradle 8.2. It has a new feature called toolchains > [1] which could be used in our project. This task is to explore that feature > consider it's usage for Kafka. > [1] https://docs.gradle.org/8.2/userguide/toolchains.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (KAFKA-15217) Consider usage of Gradle toolchain to specify Java version
[ https://issues.apache.org/jira/browse/KAFKA-15217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA reassigned KAFKA-15217: -- Assignee: Said BOUDJELDA > Consider usage of Gradle toolchain to specify Java version > -- > > Key: KAFKA-15217 > URL: https://issues.apache.org/jira/browse/KAFKA-15217 > Project: Kafka > Issue Type: Improvement >Reporter: Divij Vaidya >Assignee: Said BOUDJELDA >Priority: Minor > > We recently started using Gradle 8.2. It has a new feature called toolchains > [1] which could be used in our project. This task is to explore that feature > consider it's usage for Kafka. > [1] https://docs.gradle.org/8.2/userguide/toolchains.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KAFKA-15217) Consider usage of Gradle toolchain to specify Java version
[ https://issues.apache.org/jira/browse/KAFKA-15217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745290#comment-17745290 ] Said BOUDJELDA commented on KAFKA-15217: I feel I can take this Jira if it's possible > Consider usage of Gradle toolchain to specify Java version > -- > > Key: KAFKA-15217 > URL: https://issues.apache.org/jira/browse/KAFKA-15217 > Project: Kafka > Issue Type: Improvement >Reporter: Divij Vaidya >Priority: Minor > > We recently started using Gradle 8.2. It has a new feature called toolchains > [1] which could be used in our project. This task is to explore that feature > consider it's usage for Kafka. > [1] https://docs.gradle.org/8.2/userguide/toolchains.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (KAFKA-15217) Consider usage of Gradle toolchain to specify Java version
[ https://issues.apache.org/jira/browse/KAFKA-15217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745290#comment-17745290 ] Said BOUDJELDA edited comment on KAFKA-15217 at 7/20/23 10:22 PM: -- [~divijvaidya] I feel I can take this Jira if it's possible was (Author: JIRAUSER301378): I feel I can take this Jira if it's possible > Consider usage of Gradle toolchain to specify Java version > -- > > Key: KAFKA-15217 > URL: https://issues.apache.org/jira/browse/KAFKA-15217 > Project: Kafka > Issue Type: Improvement >Reporter: Divij Vaidya >Priority: Minor > > We recently started using Gradle 8.2. It has a new feature called toolchains > [1] which could be used in our project. This task is to explore that feature > consider it's usage for Kafka. > [1] https://docs.gradle.org/8.2/userguide/toolchains.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15222) Upgrade zinc scala incremental compiler plugin version to a latests stable fit version (1.9.2)
[ https://issues.apache.org/jira/browse/KAFKA-15222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA updated KAFKA-15222: --- Docs Text: Upgrading the version of zinc incremental scala compiler plugin, is far a good idea, since we already have an issue related to zinc probably every Gradle version upgrade since much older versions, >From the current version 1.8.0 to version 1.9.2 there may be some enhancements >there is much improvements and dependency upgrades Check this link : https://github.com/sbt/zinc/compare/v1.8.0...v1.9.2 This upgrade is too minor, and consists only on changing the version if zinc, it can be tricky since it's related to the building process and needs to be sure every things is working well, and no regression will be caused on build process was: Upgrading the version of zinc incremental scala compiler plugin, is far a good idea, since we already have an issue related to zinc probably every Gradle version upgrade since much older versions, >From the current version 1.8.0 to version 1.9.2 there may be some enhancements >there is much improvements and dependency upgrades Check this link : https://github.com/sbt/zinc/compare/v1.8.0...v1.9.2 > Upgrade zinc scala incremental compiler plugin version to a latests stable > fit version (1.9.2) > -- > > Key: KAFKA-15222 > URL: https://issues.apache.org/jira/browse/KAFKA-15222 > Project: Kafka > Issue Type: Improvement > Components: build, tools >Reporter: Said BOUDJELDA >Assignee: Said BOUDJELDA >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KAFKA-15222) Upgrade zinc scala incremental compiler plugin version to a latests stable fit version (1.9.2)
[ https://issues.apache.org/jira/browse/KAFKA-15222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745034#comment-17745034 ] Said BOUDJELDA commented on KAFKA-15222: I made a small pull request for this Jira [https://github.com/apache/kafka/pull/14060] > Upgrade zinc scala incremental compiler plugin version to a latests stable > fit version (1.9.2) > -- > > Key: KAFKA-15222 > URL: https://issues.apache.org/jira/browse/KAFKA-15222 > Project: Kafka > Issue Type: Improvement > Components: build, tools >Reporter: Said BOUDJELDA >Assignee: Said BOUDJELDA >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15222) Upgrade zinc scala incremental compiler plugin version to a latests stable fit version (1.9.2)
[ https://issues.apache.org/jira/browse/KAFKA-15222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA updated KAFKA-15222: --- Summary: Upgrade zinc scala incremental compiler plugin version to a latests stable fit version (1.9.2) (was: Upgrade zinc scala incremental compiler plugin version to a latests stable fit version ) > Upgrade zinc scala incremental compiler plugin version to a latests stable > fit version (1.9.2) > -- > > Key: KAFKA-15222 > URL: https://issues.apache.org/jira/browse/KAFKA-15222 > Project: Kafka > Issue Type: Improvement > Components: build, tools >Reporter: Said BOUDJELDA >Assignee: Said BOUDJELDA >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KAFKA-15222) Upgrade zinc scala incremental compiler plugin version to a latests stable fit version
Said BOUDJELDA created KAFKA-15222: -- Summary: Upgrade zinc scala incremental compiler plugin version to a latests stable fit version Key: KAFKA-15222 URL: https://issues.apache.org/jira/browse/KAFKA-15222 Project: Kafka Issue Type: Improvement Components: build, tools Reporter: Said BOUDJELDA Assignee: Said BOUDJELDA -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KAFKA-15000) High vulnerability PRISMA-2023-0067 reported in jackson-core
[ https://issues.apache.org/jira/browse/KAFKA-15000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744366#comment-17744366 ] Said BOUDJELDA commented on KAFKA-15000: I can take this Jira > High vulnerability PRISMA-2023-0067 reported in jackson-core > > > Key: KAFKA-15000 > URL: https://issues.apache.org/jira/browse/KAFKA-15000 > Project: Kafka > Issue Type: Bug >Affects Versions: 3.4.0, 3.3.2, 3.5.1 >Reporter: Arushi Rai >Assignee: Said BOUDJELDA >Priority: Critical > Fix For: 3.6.0 > > > Kafka is using jackson-core version 2.13.4 which has high vulnerability > reported [PRISMA-2023-0067. > |https://github.com/FasterXML/jackson-core/pull/827] > This vulnerability is fix in Jackson-core 2.15.0 and Kafka should upgrade to > the same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (KAFKA-15000) High vulnerability PRISMA-2023-0067 reported in jackson-core
[ https://issues.apache.org/jira/browse/KAFKA-15000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA reassigned KAFKA-15000: -- Assignee: Said BOUDJELDA > High vulnerability PRISMA-2023-0067 reported in jackson-core > > > Key: KAFKA-15000 > URL: https://issues.apache.org/jira/browse/KAFKA-15000 > Project: Kafka > Issue Type: Bug >Affects Versions: 3.4.0, 3.3.2, 3.5.1 >Reporter: Arushi Rai >Assignee: Said BOUDJELDA >Priority: Critical > Fix For: 3.6.0 > > > Kafka is using jackson-core version 2.13.4 which has high vulnerability > reported [PRISMA-2023-0067. > |https://github.com/FasterXML/jackson-core/pull/827] > This vulnerability is fix in Jackson-core 2.15.0 and Kafka should upgrade to > the same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (KAFKA-15208) Upgrade Jackson dependencies to version 2.15.2
[ https://issues.apache.org/jira/browse/KAFKA-15208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744284#comment-17744284 ] Said BOUDJELDA commented on KAFKA-15208: [~divijvaidya] This is the Jira for this pull request [https://github.com/apache/kafka/pull/13662] Thanks > Upgrade Jackson dependencies to version 2.15.2 > -- > > Key: KAFKA-15208 > URL: https://issues.apache.org/jira/browse/KAFKA-15208 > Project: Kafka > Issue Type: Improvement > Components: connect, kraft >Reporter: Said BOUDJELDA >Priority: Major > Labels: dependencies > > Upgrading the version of Jackson dependencies to the latest stable version > 2.15.2 can bring much bug fixing security issues solving and performance > improvement > > Check release notes back to the current version > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.15.2] > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14] > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KAFKA-15208) Upgrade Jackson dependencies to version 2.15.2
[ https://issues.apache.org/jira/browse/KAFKA-15208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Said BOUDJELDA updated KAFKA-15208: --- Flags: (was: Important) > Upgrade Jackson dependencies to version 2.15.2 > -- > > Key: KAFKA-15208 > URL: https://issues.apache.org/jira/browse/KAFKA-15208 > Project: Kafka > Issue Type: Improvement > Components: connect, kraft >Reporter: Said BOUDJELDA >Priority: Major > Labels: dependencies > > Upgrading the version of Jackson dependencies to the latest stable version > 2.15.2 can bring much bug fixing security issues solving and performance > improvement > > Check release notes back to the current version > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.15.2] > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14] > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KAFKA-15208) Upgrade Jackson dependencies to version 2.15.2
Said BOUDJELDA created KAFKA-15208: -- Summary: Upgrade Jackson dependencies to version 2.15.2 Key: KAFKA-15208 URL: https://issues.apache.org/jira/browse/KAFKA-15208 Project: Kafka Issue Type: Improvement Components: connect, kraft Reporter: Said BOUDJELDA Upgrading the version of Jackson dependencies to the latest stable version 2.15.2 can bring much bug fixing security issues solving and performance improvement Check release notes back to the current version [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.15.2] [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14] -- This message was sent by Atlassian Jira (v8.20.10#820010)
