This does have the unfortunate side effect of the plugin not complaining about a missing google-services.json unless some process<Configuration>GoogleServices task gets run somehow.
However, that may be better for local development where the answer of how to get a relevant google-services.json can be postponed until after it builds at all. (Though I understand AndroidStudio is capable of handling google-services.json, it would still be good for those forced to use CLI development only).
TESTED: Verified by a really simple local android project. Without this change, it complained about google-services.json immediately. With this change, it only complained about it if :processReleaseGoogleServices or :processDebugGoogleServices was run (directly or indirectly)
Make the processGoogleServices tasks config avoidant
See https://docs.gradle.org/current/userguide/task_configuration_avoidance.html
This does have the unfortunate side effect of the plugin not complaining about a missing
google-services.jsonunless someprocess<Configuration>GoogleServicestask gets run somehow. However, that may be better for local development where the answer of how to get a relevantgoogle-services.jsoncan be postponed until after it builds at all. (Though I understand AndroidStudio is capable of handlinggoogle-services.json, it would still be good for those forced to use CLI development only).TESTED: Verified by a really simple local android project. Without this change, it complained about
google-services.jsonimmediately. With this change, it only complained about it if:processReleaseGoogleServicesor:processDebugGoogleServiceswas run (directly or indirectly)Fixes: #180