Add call to notCompatibleWithConfigurationCache to LicensesTask #242
Conversation
This file contains 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
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.
Calling notCompatibleWithConfigurationCache on the
LicensesTaskwill prevent the build failure and instead only warn of the issue the first time it is encountered. We do arespondsTomethod check before calling it. The method was added as incubating in Gradle 7.4 and may be removed in a future version.We use the Project object during
LicensesTaskexecution to query the location of POM files and any Play Services SDKs to extract license information. We don't know which artifact IDs to use in those queries until the AGP task that produces the information has run. It's a bit of a circular problem, but we can at least prevent the build halting error.Running repeated builds still results in <= 1 second build time for a test project.
fix #206