Use foojay-resolver-convention to resolve JVM toolchains #238
Conversation
|
Why use a toolchain when any modern JDK can cross-compile to Java 8 with faster compilation speeds and bytecode generation bugfixes using the |
@JakeWharton, it's just more convenient compared to explicitly specifying the target for all kotlin- and java-tasks. |
|
@JakeWharton, I would also prefer to use flags, however, not all of our agents have JDK installed on which the flag @fzhinkin, could you clarify a little bit why we are limiting the JDK version? To make the BCV plugin work if Gradle runs on older JVMs? |
|
@shanshin, yes, the version is limited for Gradle compatibility reasons (it works with Java >= 8). |
|
At the same time, according to our Readme, Java >= 11 is required to use BCV :) |
…ains * Use foojay-resolver-convention to resolve JVM toolchains * Remove no longer needed java toolchain setup Pull request Kotlin/binary-compatibility-validator#238
…ains * Use foojay-resolver-convention to resolve JVM toolchains * Remove no longer needed java toolchain setup Pull request Kotlin/binary-compatibility-validator#238
…ains * Use foojay-resolver-convention to resolve JVM toolchains * Remove no longer needed java toolchain setup Pull request Kotlin/binary-compatibility-validator#238
…ains * Use foojay-resolver-convention to resolve JVM toolchains * Remove no longer needed java toolchain setup Pull request Kotlin/binary-compatibility-validator#238 Moved from Kotlin/binary-compatibility-validator@33a495b
…ains * Use foojay-resolver-convention to resolve JVM toolchains * Remove no longer needed java toolchain setup Pull request Kotlin/binary-compatibility-validator#238 Moved from Kotlin/binary-compatibility-validator@33a495b
Recently, I was running BCV tests on hosts with only recent Java installed, and automatic toolchain provisioning could made my life much easier.