This message was deleted.
# community-supports
Slackbot
05/06/2022, 4:16 PMThis message was deleted.
c
Chris Lee
05/06/2022, 4:18 PMYou can use the toolchain capabilities to separate the JVM used for Gradle from the JDK used to compile your code.
s
Simon Kågedal Reimer
05/06/2022, 4:25 PMYup, I know! But not actually run Gradle if my JAVA_HOME is too new.
t
Thomas Broyer
05/06/2022, 4:25 PM*Y*ou might have to also disable incremental compilation, as it uses ASM to post-process compiled classes.
v
Vampire
05/06/2022, 10:45 PMGradle does not post-process compiled classes, does it?
It pre-processes, analyzing the dependencies for whether there was an ABI change and so on. But it should not change the compiled classes, or does it?
Vampire
05/06/2022, 10:47 PMAnd regarding the initial question, it can always be, that a new Java version works or does not work. Like with any Java program, it can be compatible with a newer Java version or it can have problems that need to be fixed. And yes, if you use Groovy DSL or plugins written in Groovy, it could well be that there the compatibility also has problems. One of the reasons I would always just use plain Java in the lowest version supported by the lowest version of Gradle that should be supported to be as compatible as possible.
t
Thomas Broyer
05/06/2022, 11:21 PMGradle does not post-process compiled classes, does it?
It pre-processes, analyzing the dependencies for whether there was an ABI change and so on. But it should not change the compiled classes, or does it?It process them after compilation (obviously) to analyze dependencies, so "post process", and will use that analysis in subsequent compilations to determine which classes need to be recompiled given modified files. But it does not modify the compiled classes indeed.
👌 1
3 Views