dejan2609 commented on PR #21372: URL: https://github.com/apache/kafka/pull/21372#issuecomment-3938452788
Just an update: it seems that the issue mentioned above by @chia7712 is a corner case. In my own setup spotless task execution is working just fine (see console output below). Conclusion: I will try to dig around and to provide more information for the Spotless team. ``` dejan@box:~/kafka$ date Sat 21 Feb 09:22:08 CET 2026 dejan@box:~/kafka$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04.4 LTS Release: 24.04 Codename: noble dejan@box:~/kafka$ uname -r 6.8.0-100-generic dejan@box:~/kafka$ git log -2 --oneline 9d16751ffc (HEAD -> Gradle-9.3.1, origin/Gradle-9.3.1) MINOR: Gradle version update: 9.2.1 -->> 9.3.1 2df7c75fd5 MINOR: Fix requests version conflict with ducktape in tests/setup.py (#21415) dejan@box:~/kafka$ ./gradlew clean spotlessCheck > Configure project : Starting build with version 4.3.0-SNAPSHOT (commit id 9d16751f) using Gradle 9.3.1, Java 17 and Scala 2.13.18 Build properties: ignoreFailures=false, maxParallelForks=8, maxScalacThreads=8, maxTestRetries=0 [Incubating] Problems report is available at: file:///home/dejan/kafka/build/reports/problems/problems-report.html Deprecated Gradle features were used in this build, making it incompatible with Gradle 10. 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/9.3.1/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. BUILD SUCCESSFUL in 14s 196 actionable tasks: 196 executed Consider enabling configuration cache to speed up this build: https://docs.gradle.org/9.3.1/userguide/configuration_cache_enabling.html dejan@box:~/kafka$ date Sat 21 Feb 09:22:51 CET 2026 dejan@box:~/kafka$ ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
