[
https://issues.apache.org/jira/browse/KAFKA-21326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18129875#comment-18129875
]
Dejan Stojadinović edited comment on KAFKA-21326 at 11/2/26, 1:01 PM:
----------------------------------------------------------------------
I tried to figure out would it be possible to disable configuration cache in
Gradle 10 and it seems that priorities are changed: Gradle will push
enablement-by-a-default for this feature to Gradle 11:
*
[https://adtmag.com/articles/2026/08/27/gradle-shifts-build-tool-priorities-as-ai-coding-agents-become-users.aspx]
* [https://blog.gradle.org/gradle-is-going-agentic]
{quote}*We're making Gradle work well with coding agents, and that meant not
shipping Configuration Cache by default in Gradle 10 this cycle.*
{quote}
This probably means that configuration cache will not be mandatory for a quite
a long time (probably not even in Gradle 11) and hence issue link to
KAFKA-20102 is removed.
*However: configuration cache is the preferred mode of execution since Gradle
9.0.0:*
*
[https://blog.gradle.org/road-to-configuration-cache#preferred-mode-of-execution]
*
[https://docs.gradle.org/9.7.1/userguide/best_practices_performance.html#use_configuration_cache]
so it makes sense to push forward with this ticket.
was (Author: dejan2609):
I tried to figure out would it be possible to disable configuration cache in
Gradle 10 and it seems that priorities are changed: Gradle will push
enablement-by-a-default for this feature to Gradle 11:
*
[https://adtmag.com/articles/2026/08/27/gradle-shifts-build-tool-priorities-as-ai-coding-agents-become-users.aspx]
* [https://blog.gradle.org/gradle-is-going-agentic]
{quote}*We're making Gradle work well with coding agents, and that meant not
shipping Configuration Cache by default in Gradle 10 this cycle.*
{quote}
This probably means that configuration cache will not be mandatory for a quite
a long time (probably not even in Gradle 11) and hence issue link to
KAFKA-20102 is changed from _*blocks*_ to _*relates to*_
*However: configuration cache is the preferred mode of execution since Gradle
9.0.0:*
*
[https://blog.gradle.org/road-to-configuration-cache#preferred-mode-of-execution]
*
[https://docs.gradle.org/9.7.1/userguide/best_practices_performance.html#use_configuration_cache]
so it makes sense to push forward with this ticket.
> Enable Gradle configuration cache
> ---------------------------------
>
> Key: KAFKA-21326
> URL: https://issues.apache.org/jira/browse/KAFKA-21326
> Project: Kafka
> Issue Type: Task
> Reporter: Dejan Stojadinović
> Assignee: Dejan Stojadinović
> Priority: Minor
> Labels: gradle
> Attachments: image-2026-10-22-00-05-06-519.png
>
>
> [https://docs.gradle.org/9.7.1/userguide/configuration_cache.html]
> {quote}
> -This feature will be enabled by default in Gradle 10.- [see comment
> below|https://issues.apache.org/jira/browse/KAFKA-21326?focusedId=18129875&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-18129875]
> {quote}
> !image-2026-10-22-00-05-06-519.png!
>
>
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
