I have been suddenly getting this error without even changing the build.gradle or META-INF/mods.toml files. What does it mean by that? Aren't we supposed to use Java 17 for our 1.18.2 mods? I use IntelliJ, and I invalidated caches restarted, but it didn't work. I also made sure my JVM and JDK were both version 17. Was there something I needed to update?

This is the output when I run ./gradlew --warning-mode=all build

> Configure project :
Java: 17.0.2, JVM: 17.0.2+8-LTS-86 (Oracle Corporation), Arch: x86_64
Resolution of the configuration :runtimeClasspathCopy was attempted from a context different than the project context. Have a look at the documentation to understand why this is a problem and how it can be resolved. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. See https://docs.gradle.org/7.4/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors for more details.
Resolution of the configuration :minecraftCopy was attempted from a context different than the project context. Have a look at the documentation to understand why this is a problem and how it can be resolved. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. See https://docs.gradle.org/7.4/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors for more details.
Resolution of the configuration :runtimeClasspathCopy2 was attempted from a context different than the project context. Have a look at the documentation to understand why this is a problem and how it can be resolved. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. See https://docs.gradle.org/7.4/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors for more details.
Resolution of the configuration :minecraftCopy2 was attempted from a context different than the project context. Have a look at the documentation to understand why this is a problem and how it can be resolved. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. See https://docs.gradle.org/7.4/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors for more details.
Resolution of the configuration :runtimeClasspathCopy3 was attempted from a context different than the project context. Have a look at the documentation to understand why this is a problem and how it can be resolved. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. See https://docs.gradle.org/7.4/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors for more details.
Resolution of the configuration :minecraftCopy3 was attempted from a context different than the project context. Have a look at the documentation to understand why this is a problem and how it can be resolved. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. See https://docs.gradle.org/7.4/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors for more details.
Resolution of the configuration :runtimeClasspathCopy4 was attempted from a context different than the project context. Have a look at the documentation to understand why this is a problem and how it can be resolved. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. See https://docs.gradle.org/7.4/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors for more details.
Resolution of the configuration :minecraftCopy4 was attempted from a context different than the project context. Have a look at the documentation to understand why this is a problem and how it can be resolved. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. See https://docs.gradle.org/7.4/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors for more details.

> Task :compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> error: release version 17 not supported

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 4s
1 actionable task: 1 executed

 

Edited April 3, 20223 yr by LeeCrafts

I...barely even know what I just did. I ran ./gradlew -q javaToolchains saw the paths to all my JDKs. Then I navigated through those paths (you have to do it via Terminal) and manually deleted the JDKs I didn't need. 

Java: 17.0.2, JVM: 17.0.2+8-86 (Oracle Corporation), Arch: x86_64

 + Options
     | Auto-detection:     Enabled
     | Auto-download:      Enabled

 + OpenJDK 17.0.2+8-86
     | Location:           /Users/wlee2019/Library/Java/JavaVirtualMachines/openjdk-17.0.2/Contents/Home
     | Language Version:   17
     | Vendor:             Oracle
     | Architecture:       x86_64
     | Is JDK:             true
     | Detected by:        Current JVM

 + Oracle JDK 17.0.2+8-LTS-86
     | Location:           /Library/Java/JavaVirtualMachines/jdk-17.0.2.jdk/Contents/Home
     | Language Version:   17
     | Vendor:             Oracle
     | Architecture:       x86_64
     | Is JDK:             true
     | Detected by:        macOS java_home

 + Oracle JRE 1.8.0_321-b07
     | Location:           /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
     | Language Version:   8
     | Vendor:             Oracle
     | Architecture:       x86_64
     | Is JDK:             false
     | Detected by:        macOS java_home

This is the output I currently have, but it had a lot more unnecessary stuff. I guess the gradlew build ran on the wrong "Current JVM."

Edited April 3, 20223 yr by LeeCrafts