You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of Spring Boot 2.4.1 and Grade 6.7.1, BootRun is assuming that the JVM that will be running the application is the same as the version running Gradle. The toolchain support means this may no longer be the case.
This leads to the re-appearance of a warning message first addressed in this fix: scope-demo@af223c2
When running Gradle in Java8 and targeting Java15, the warning message arises due to the inclusion of the deprecated -Xverify:none parameter.
wilkinsona
changed the title
BootRun does not consider configured javaLauncher
BootRun does not consider configured javaLauncher when determining JVM arguments for an optimized launch
Dec 15, 2020
As of Spring Boot 2.4.1 and Grade 6.7.1,
BootRun
is assuming that the JVM that will be running the application is the same as the version running Gradle. The toolchain support means this may no longer be the case.This leads to the re-appearance of a warning message first addressed in this fix:
scope-demo@af223c2
When running Gradle in Java8 and targeting Java15, the warning message arises due to the inclusion of the deprecated
-Xverify:none
parameter.More details and minimal repro here: https://github.com/jeffbswope/spring-boot-grade-toolchain
The text was updated successfully, but these errors were encountered: