dweiss commented on PR #12131: URL: https://github.com/apache/lucene/pull/12131#issuecomment-2084491642
> I'm happy to report that we can put individual settings in ~/.gradle/gradle.properties and these settings will overlay in priority over those in the project's properties. Nice; ehh? Sorry, I wasn't clear - this option has been possible since the very beginning of gradle. The problem is that it's a global setting and, if I recall right, we wanted to have the possibility to set those options locally, per-project. It may seem like a no-brainer to set those parallel worker (or test jvms) globally but it's tricky. Many people won't know about it or bother and - what's even more problematic - it's a global setting, it'll affect you if you have other projects with very heavy tests. Then forking the same number of gradle or test workers would result in an OOM for one project but not for others. It would be ideal if you could specify something like what we had for ant previously - a "gradle.properties.local" but this isn't possible. Can I ask why is that automatically generated gradle.properties file bothering you? You can "override" those per-project settings with your global gradle.properties file or env variables [1], if you don't have a problem with sharing those settings across projects. [1] https://docs.gradle.org/current/userguide/build_environment.html#sec:gradle_configuration_properties -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
