This may help you understand the hierarchy of how properties are shadowing each other. https://docs.gradle.org/current/userguide/build_environment.html
The discussion concerning project properties that people could "override" locally concerned the settings set in the global gradle.properties file -- this was something I wasn't too happy with if they clashed with other projects. For now the gradle build doesn't have any means to populate certain properties with custom values (other than command-line). If there is a need for it we can add it. Dawid On Tue, Dec 3, 2019 at 11:48 PM Erick Erickson <[email protected]> wrote: > > Thanks, I’m still untangling the various bits Mark put in and > relying on people who actually, you know, understand > things ;) > > > On Dec 3, 2019, at 5:11 PM, Dawid Weiss <[email protected]> wrote: > > > >> // the project version > >> version=9.0.0 > > > > You shouldn't have it in your global configuration. In fact, only > > these make sense in there: > > > > org.gradle.daemon=true > > org.gradle.workers.max = 6 > > > > The cache and daemon settings I'd leave to the project's config. > > > > Dawid > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
