This message was deleted.

Some things we may want to define as default: •

org.gradle.java.installations.fromEnv

•

org.gradle.java.installations.paths

•

org.gradle.workers.max

•

org.gradle.jvmargs

I think if you talk about such fundamental settings as

org.gradle.jvmargs

the best (only?) option is to use the installation dir. What we did in a company with many Gradle projects is to create a custom distribution. We wanted to make Gradle available for download in the company network anyway. So we now put gradle-bin.zip versions into the company internal artifactory. Before we upload them, they are enriched with the shared

gradle.properties

file (add it to the root of the zip, and it will be in the root of the installation). In the

gradle-wrapper.properties

of all projects, we have the URL pointing at the gradle-bin.zip inside the company artifactory. Our main use case was not about overriding values though. We wanted an automated way to share the values with all users without them having to manually maintain something in their user home. And without having to duplicate the same

gradle.properties

file in ~200 git repos.

Wow, thanks for sharing. But that seems like a lot of work just to share some properties! 🤔 In any case, using a custom distribution is not really an option for the use case I'm describing. If I want to provide CI build machines, and I don't control the users' choice of gradle wrapper, I would still like to be able to pre-configure

org.gradle.java.installations.paths

for instance, to point to my pre-installed JDKs. But I would need to do this in a way that doesn't override the user's project-specific choice (if they have chosen to use this gradle property already to point to a special JDK that they install in a specific place, for instance).