On Mon, 3 Aug 2026 15:05:26 GMT, Anirvan Sarkar <[email protected]> wrote:
>> Allows using a Gradle properties file at the project level by requiring the >> user-specific one to be present in the user's Gradle dir. A Gradle >> properties file is necessary for a proper Gradle build system's >> configuration. The user file takes precedence over the project one. >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > I have a concern about requiring OpenJFX specific configuration in the > user-level `~/.gradle/gradle.properties`. > > This makes OpenJFX build properties visible to every Gradle build on the > machine. > In particular, generically named project defined properties such as > `JDK_HOME`, `CONF`, `INCREMENTAL`, and `LINT` could conflict with unrelated > projects or plugins. > > It also prevents developers from keeping OpenJFX only Gradle settings scoped > to this repository, for example: > > > org.gradle.java.home=C:/JDK/jdk-25.0.1 > org.gradle.dependency.verification=lenient > org.gradle.daemon=false > > > Is there a reason we cannot continue to support a project local, gitignored > `gradle.properties` instead? > This would still allow each developer to configure their own environment > while keeping the configuration isolated to the OpenJFX build. I have the same concern as @AnirvanSarkar ------------- PR Comment: https://git.openjdk.org/jfx/pull/2240#issuecomment-5170741869
