Hi Ulrich,
I don't know if it would work in this context, but it seems reasonable
to hope that Gradle's Java Toolchains
(https://docs.gradle.org/current/userguide/toolchains.html) might help
in this scenario. I've not tried using multiple toolchains within a
single multi-project build, but gi
Yes, that is exactly what I'm looking for. But I take it that Netbeans
doesn't support that via the UI?
So maybe I should define gradle tasks that run with
"-Dorg.gradle.java.home=/JDK_PATH" or something like that? But it seems
wrong to code filesystem paths into the buildfile, because those w
maybe it is better to use different release labels/settings in the super or
subproject.
in that scenario, choose the highest acceptable version as the base version
and 'downgrade' the release in the submodules that require it.
met vriendelijke groet
Pieter van den Hombergh
Op di 4 mrt 2025, 12
