Update to Gradle 9 and make more progress toward configuration cache compatibility #2695
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…me things for TC.
…radle will create the build/deploy/modules directory even if empty
labkey-tchad
approved these changes
Sep 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rationale
Gradle 9.0.0 has been released (and 9.1.0 is coming soon). This release has removed some deprecated features and moves even closer to making the use of the configuration cache the default behavior, so getting out build closer to compatibility will help make the transition easier whenever that happens (Probably Gradle 10, but I'm unsure on the timing of that).
Related Pull Requests
Changes
initPropertiestask to aCopytaskdata/qctasks for better cachingTestFileUtils.getModulesDirto first look for the embedded modules directory then thebuild/deploy/modulesdirectory (not strictly necessary, but seems reasonable so we aren't tripped up again bybuild/deploy/modulesgetting created even if it doesn't have modules in it).