Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve Gradle configurations cache issues #731

Merged
merged 1 commit into from
Jul 28, 2023

Conversation

JoelWilcox
Copy link
Member

  • Update our 'generateBuildProperties' tasks to be configuration cache compatible
  • Remove an old task check around absolute file paths. The use of 'afterTask' causes failures when configuration cache is used, and Gradle's recommended replacement does not cleanly replace the deprecated method since it no longer provides access to the 'Task' instance. Based on previous comments around intention to remove this check, we should be fine without this.

- Update our 'generateBuildProperties' tasks to be configuration cache compatible
- Remove an old task check around absolute file paths. The use of 'afterTask' causes failures when configuration cache is used, and Gradle's recommended replacement does not cleanly replace the deprecated method since it no longer provides access to the 'Task' instance. Based on previous comments around intention to remove this check, we should be fine without this.
@JoelWilcox JoelWilcox marked this pull request as ready for review July 28, 2023 18:21
@JoelWilcox JoelWilcox merged commit 912367e into main Jul 28, 2023
19 checks passed
@JoelWilcox JoelWilcox deleted the joel.configuration-cache-fixes branch July 28, 2023 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants