Can someone help me with : * What went wrong: Con...
# community-support
i
Can someone help me with : * What went wrong: Configuration cache problems found in this build. 4 problems were found storing the configuration cache, 2 of which seem unique. - Task
:helprooms:initQuerydslSourcesDir
of type `com.ewerk.gradle.plugins.tasks.InitQuerydslSourcesDir`: invocation of 'Task.project' at execution time is unsupported. See https://docs.gradle.org/8.6/userguide/configuration_cache.html#config_cache:requirements:use_project_during_execution - Task
:hotlines:initQuerydslSourcesDir
of type `com.ewerk.gradle.plugins.tasks.InitQuerydslSourcesDir`: invocation of 'Task.project' at execution time is unsupported. See https://docs.gradle.org/8.6/userguide/configuration_cache.html#config_cache:requirements:use_project_during_execution
m
I can see several options: • the QueryDsl plugin you're using is ancient. You can try to find a modern replacement, though my search on the plugin portal didn't show anything particularly appealing. • You can mark broken tasks with
notSupportedWithConfigurationCache
in your build script, but you won't get benefits of the configuration cache when these tasks run. As these seem to be part of the code generation, you'll be likely as good as not enabling CC at all. • Of course, you can write your own plugin or fork and fix the one you're using.
given that the querydsl seems to be just an annotation processor, setting it up shouldn't be too hard.
i
Thank you, I have been trying to do so, but unsuccessful
I have upgraded our gradle 7 to 8 for seek of build improvement
v
Like you do since quite some time. You asked this exact same question a month ago. And I already back then told you, that this plugin is not compatible with what you try to do. And in the end you even said you "found the root cause". o_O