If I add

foo=bar

to my root project

gradle.properties

, how is this working if this same root project becomes an included build? 1. The main build value is used 2. The included build value is used 3. It depends If 3., how can I tell?

4. Obiwan Kenobi

looks like included build uses its own properties. same for root.

> Configure project :plugins
IncludedBuild foo=included

> Configure project :
RootBuild foo=rootProject

I mean for some of them it makes almost no sense I think? There can be only one

org.gradle.jvmargs

for an example

in my project I usually just put a sane default in each gradle.properties, then in CI when I need to have them updated I just calculate the value once into a bash var and pass it via -P for subsequent builds. Typically only do this for version value when publishing to jfrog. The usecase I had in that thread was for the most part made moot by using a shared toml file across all the builds in our main repo.

Thanks! I think I will just continue duplicating my gradle.properties for now.

> I think I will just continue duplicating my gradle.properties for now. Best approach > I mean for some of them it makes almost no sense I think? There can be only one

org.gradle.jvmargs

for an example This is related to the fact that the included build is built using the same JVM & Gradle as the starting root project. This might change in future, but it is state thing at present.