Open TheElan opened 2 years ago
We might want to consider rolling back to using if-throw exception on gradle evaluation if incorrect java is used (this means you need gradle to run on this java entirely, in comparison toolchain only forces it in some tasks), this way it will fail much faster.
Yes. I think this is the way to go, untill all forge Gradle tasks can be converted to toolchains from Gradle 6
Try to find out what causes wired behaviour, on system where only jre was present and dev used a bundled version of 11th in IDEA there was a problem of gradle not downloading jdk and attempting to use jre.
Running
./gradlew build
should ensure proper java setupTest cases to try out:
Fiddle with PATH and JAVA_HOME (empty, present (pointing to java install dir), absent)