Gradle quarkusGenerateCode
runs far too often
#41404
Labels
Milestone
quarkusGenerateCode
runs far too often
#41404
Describe the bug
When using Gradle to build a Quarkus app, the
quarkusGenerateCode
task is almost never cached. Even on successive runs of the same codebase without any code changed, this job will rerun - even on codebases where no code is actually being generated.I managed to boil it down to the following:
cachingRelevantInput
andinternalTaskConfig
are often found to be "changed". These values are provided by the task here. These values are provided as a normal map.So I think on the Quarkus side, it is best to move to a map implementation that guarantees order of some kind - or find some other way to convince Gradle the task can reuse the cached result. In addition, I feel like the scope of the
cachingRelevantInput
map is too large: it includes all system properties prefixed byquarkus.
, even those not affecting code generation at all. It might be good to look into reducing this scope as well.Output of
uname -a
orver
Linux FLORIS-NORTH 4.4.0-22621-Microsoft #3672-Microsoft Fri Jan 01 08:00:00 PST 2016 x86_64 x86_64 x86_64 GNU/Linux
Output of
java -version
openjdk version "17.0.10" 2024-01-16
Quarkus version or git rev
3.11
Build tool (ie. output of
mvnw --version
orgradlew --version
)8.8
The text was updated successfully, but these errors were encountered: