From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Is ditching the idea of configuring things in the root build.gradle and switching to gradle properties instead the way to go here?

Hi Eric,
We're working on designing replacements for `allprojects {}` and such for central configuration that will work with project isolation but nothing ready as of Today. In the current state of project isolation, using Gradle properties would work.

In this specific case, maybe using a settings plugin (configuring the extension in settings.gradle rather than the root build.gradle) would work (and possibly using a build service to share that value across projects) ?

Using a build service to share the state should also work yes

It could be configured from settings or from the root project. The root project is always configured first. Moving the configuration to settings would make more sense to me though as it looks like what you're doing Eric is a global _setting_ for the whole build :thumbsup:

Update: switched over to a settings plugin + build service and the result is perfect. Thanks again!