Architecture change to support configuration cache in a proper way

[ILikeYourHat]

Architecture change to support configuration cache in a proper way

[mikepenz]

Good day @ILikeYourHat

Thank you for the report. The last few weeks have been very busy and I haven't had a chance to look more into it, and I am not sure yet when I will be able to.

A possible work-around for all those problems may be to disable the registration as part of the android build pipelines, and having the CI build the dependencies (or making it a step of the release process) with the results to be included as part of the SCM.

I agree though that there are problems to the caching, specifically the configuration cache system. I see that there are updates being made in gradle in regards to retrieving the information we need, but so far past tries have not been sufficient.

At this current time I may not be able to spend the amount of time on this matter, as I'd need to, to find a proper solution for all scenarios.

That being said, if somebody with more time, or more knowledge about gradle would like to look into this. It would be immensely appreciated.