On Fri, 28 Aug 2026 13:05:03 GMT, Marius Hanl <[email protected]> wrote:
> I wonder if we could do that in the settings.gradle instead? Probably, but it has Oracle's `buildClosed` configuration there that I didn't want to conflict with. I try to go for minimal friction for the time being. This step is crucial for freeing the *de-facto* properties file for its intended use, which will allow to use the proper Java toolchain and enable parallel builds and caches. When things are wired up correctly and the entanglement reduces, we can have a look at this again. The solution there is probably for Oracle to unify whatever it is they are doing in there with the public hooks that are provided, like this one. > To be honest I don't know that the best practise is (or if there even is > 'best way'), just something I was wondering The best practice for what? Reading a user's properties file? Not that I know of. The Gradle team admits it's a gap, they're just not sure what to do about it. See https://github.com/gradle/gradle/issues/12283. ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/2240#discussion_r3903992366
