Closed pstavytskyi-turo closed 1 year ago
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Pavlo Stavytskyi. This is most likely caused by a git client misconfiguration; please make sure to:
git config --list | grep email
git config --global user.email email@example.com
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Pavlo Stavytskyi. This is most likely caused by a git client misconfiguration; please make sure to:
git config --list | grep email
git config --global user.email email@example.com
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Pavlo Stavytskyi. This is most likely caused by a git client misconfiguration; please make sure to:
git config --list | grep email
git config --global user.email email@example.com
Hey @rorbech , @cmelchior could you please take a look at this PR? Thanks!
Hi @pstavytskyi-turo. Thanks for the contribution. I have replaced this PR with #7753 to get CI validation of the PR.
Description
This PR fixes Gradle Configuration Cache support of Realm Gradle Plugin. Related to this issue: https://github.com/realm/realm-java/issues/7299
Problem
Currently, the
-transform-api
versions of Realm do not support Gradle Configuration Cache. The reason is thatModifyClassesTask
class in Realm Gradle Plugin uses a reference toProject
object which is something that is now allowed by Config Cache. The build fails with the error below:Solution
The solution is to move all of the usages of
Project
object out of the Gradle task at the registration step. This way, Configuration cache works as expected. Tested with AGP 8.0