On Fri, 25 Sep 2026 19:43:05 GMT, Michael Strauß <[email protected]> wrote:
>>> But that's already the case for the main build, with the expectation that >>> the daemon runs an appropriate JVM. Why do this in a subproject now? >> >> It's not. The build forks a JVM and executes the JavaFX build CLI-style. I >> don't think there's a restriction on the daemon JDK except that it can run >> the Gradle version that is used. > > Right, and the script skips JDK detection and forking for the new subproject > in `allprojects`. What's the reason that you opted out of this path? I don't want more projects using the incorrect path. It will increase the technical debt. ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/2156#discussion_r4108459454
