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
Until now, before the execution of any Gradle task, there are some validations about the project Gradle JDK configuration happening this logic on LocalGradleExecutionAware.prepareJvmForExecution() and throwing an exception if isn’t possible to resolve the defined gradleJvm from a known macro or jdk.table.xml entry. However, when the Gradle daemon toolchain criteria is defined with a compatible Gradle version, this must bypass the existing validations, delegating any validation to Gradle which will throw any exception regarding the defined criteria as well as other related exceptions.
The text was updated successfully, but these errors were encountered:
Until now, before the execution of any Gradle task, there are some validations about the project Gradle JDK configuration happening this logic on LocalGradleExecutionAware.prepareJvmForExecution() and throwing an exception if isn’t possible to resolve the defined gradleJvm from a known macro or jdk.table.xml entry. However, when the Gradle daemon toolchain criteria is defined with a compatible Gradle version, this must bypass the existing validations, delegating any validation to Gradle which will throw any exception regarding the defined criteria as well as other related exceptions.
The text was updated successfully, but these errors were encountered: