Opt all tasks out of tracking and configuration caching. #20
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.
Resolves #4.
See https://docs.gradle.org/current/userguide/configuration_cache.html for more information.
The point of
notCompatibleWithConfigurationCache("Uses Project at execution time")
is to tell Gradle that, if a user tries to run this task with the flagorg.gradle.unsafe.configuration-cache=true
set, then that flag should be ignored. Without that method call, then Gradle would instead fail the build. This lets users say they want CC on by default, while gracefully falling back to having it off for tasks that aren't compatible. Otherwise, they'd have to remember it doesn't work for tasks X, Y, and Z, and manually use--no-configuration-cache
, which is annoying.As an aside, something weird is happening with this project's .gitignore files. I had to manually add both files in the
utils
package.I think it's the gitignore rule to ignore simply
gradle
.