Related
While running a script, I am getting the following error message in the Eclipse console:
Class has been compiled by a more recent version of the Java Environment (class file version 53.0), this version of the Java Runtime only recognizes class file versions up to 52.0.
Java Version: 8
IDE: Eclipse Oxygen
Firefox Version: 46
This is just a version mismatch. You have compiled your code using java version 9 and your current JRE is version 8. Try upgrading your JRE to 9.
49 = Java 5
50 = Java 6
51 = Java 7
52 = Java 8
53 = Java 9
54 = Java 10
55 = Java 11
56 = Java 12
57 = Java 13
58 = Java 14
59 = Java 15
60 = Java 16
61 = Java 17
62 = Java 18
63 = Java 19
IDE: Eclipse Oxygen.3
To temporarily correct the problem do the following:
Project menu > Properties > Java Compiler > Compiler compliance level > 1.8
A permanent fix likely involves installing JDK 9.
FYI 1.8 is what Java 8 is called.
Side bar
I recently returned to Java after a foray into C# (a breath of fresh air) and installed Eclipse Oxygen onto a clean system that had never had Java installed on it before. This default everything with a brand new install of Eclipse Oxygen yet somehow or other Eclipse can't get its own parameters to match the jdk that's installed. This is the second project I created and the second time I ran into this headache. Time to go back to C#?
Related Question
has been compiled by a more recent version of the Java Runtime (class file version 53.0)
You might see this error in IntelliJ as well and this comes up in Google.
I think it's a Gradle error more than an IDE error.
The fix (stolen from here) is configure Java 11 as a Gradle JVM in IntelliJ:
File -> Settings -> Build, Execution & Development -> Build Tools -> Gradle and change Gradle JVM to 11
That screenshot stolen from the Jetbrains issue as well
You can try this way
javac --release 8 yourClass.java
For Android Studio, File -> Project Structure [Ctrl + Alt + Shift + S]
53 stands for java-9, so it means that whatever class you have has been compiled with javac-9 and you try to run it with jre-8. Either re-compile that class with javac-8 or use the jre-9
For temporary solution just right click on Project => Properties => Java compiler => over there please select compiler compliance level 1.8 => .class compatibility 1.8 => source compatibility 1.8.
Then your code will start to execute on version 1.8.
I had a similar issue from the console after building a Jar in Intellij. Using the Java configuration to update to a newer version (Windows -> Configure Java -> Update -> Update Now) didn't work and stuck at version 1.8 (Java 8).
To switch to a more recent version locally I had to install the Java 15 JDK from https://www.oracle.com/uk/java/technologies/javase-jdk15-downloads.html and add that to my Java runtime environment settings.
The solution for me was doing what Andrei Kuznetsov said at https://youtrack.jetbrains.com/issue/IDEA-251407/Failed-to-run-Android-project-in-the-Idea-20203-EAP-OutputBuildAction-has-been-compiled-by-a-more-recent-version-of-the-Java, summarized in the following image:
"Root cause: IDEA sources are now compiled against Java 11. Known workaround is to configure Java 11 as a Gradle JVM." (Andrei Kuznetsov)
Your JDK version: Java 8
Your JRE version: Java 9
Here your JRE version is different than the JDK version that's the case. Here you can compile all the java classes using JDK version 1.8. If you want to compile only one java class just change the *.java into <yourclassname>.java
javac -source 1.8 -target 1.8 *.java
source: The version that your source code requires to compile.
target: The oldest JRE version you want to support.
I'm writing this because I found the other answers hard to understand.
Essentially your JRE is not updated and/or Eclipse is not configured to use the most recent JRE.
On Windows, go to Control Panel -> Programs -> Java -> update and proceed to update java
or if you don't have Java, go to Oracle's website and download the most recent JRE.
Once this is done, go into eclipse, and under the project view, right click on your project, select Java Build Path, double click on JRE System Library, then Select Workspace Default JRE 14.1.
If a recent version of Java doesn't show up here, it probably isn't installed. Check you JRE(NOT JDK) version and make sure it's recent. If it is, try restarting the computer then trying this again.
IDE : Eclipse 2021-09
This is caused because you have compiled the code with java version 9 and have java8 installed. You don't have to update to solve this issue.
Right click on project > properties > Java Compiler > untick-Enable
project specific settings > configure workspace settings > tick-Use
default compliance settings > Apply and Close.
Now your code should be executed properly.
I've reproduced on Windows 10 the similar issue in format like:
Error: LinkageError occurred while loading main class ...
java.lang.UnsupportedClassVersionError: com/.../ServiceApplication
has been compiled by a more recent version of the Java Runtime (class file version 62.0),
this version of the Java Runtime only recognizes class file versions up to 61.0
after upgrading the project from Java 17 to Java 18.
I had project settings regarding to Java 18:
Command line:
java version "18.0.1.1" 2022-04-22
Java(TM) SE Runtime Environment (build 18.0.1.1+2-6)
Java HotSpot(TM) 64-Bit Server VM (build 18.0.1.1+2-6, mixed mode, sharing)
Project Structure -> Project Settings -> Project:
Project Structure -> Project Settings -> Modules:
Project Structure -> Platform Settings -> SDKs:
And the reason of this issue was:
I forgot to specify the correct version for Run/Debug Configurations -> Build and run to Java 18 instead of Java 17:
As it was compiled with a newer Java version, but running on the older one.
If it's Maven-related issue, you can modify POM by specifying the -source and -target of the Java Compiler.
Additional helpful links:
Setting the Java Version in Maven
Consuming Jar Artifact of a Specific Java Version
Go to Project section, click on properties > then to Java compiler > check compiler compliance level is 1.8 , or there should be no yellow warning at bottom
Refreshing gradle dependencies works for me: Right click over the project -> Gradle -> Refresh Gradle Project.
You should check your Project Facets.
Project Properties > Project Facets
Change java version to the same version you are using. That work for me!
I faced this error in Intellij. Apparently, choosing java 1.8 as the project SDK doesn't affect the javac compiler that's used to build the project.
To change that, go to Settings -> Build, Execution, Deployment -> Compiler -> Java Compiler, and change Project bytecode version to 8.
If you're using IntelliJ IDEA and having this error, try this.
Command + , (Open Preferences)
Build, Execution, Deployment > Build Tools > Gradle
Gradle JVM > Change it to a proper version
This is getting as an example
if your computer running on an older version of java and the Neo4J is compiled on the latest version, please try to install the same version or upper to your computer.
I'm getting the same problem with Sonarqube
has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
Sonarqube with AzureDevOps error output:
INFO: SonarScanner 4.6.2.2472
INFO: Java 1.8.0_231 Oracle Corporation (32-bit)
INFO: Windows Server 2016 10.0 x86
INFO: User cache: C:\Windows\system32\config\systemprofile.sonar\cache
INFO: Scanner configuration file: C:\agent_a_work_tasks\SonarQubePrepare_15b84ca1-b62f-4a2a-a403-89b77a063157\5.4.0\classic-sonar-scanner-msbuild\sonar-scanner-4.6.2.2472\bin..\conf\sonar-scanner.properties
INFO: Project root configuration file: C:\agent_a_work\189.sonarqube\out\sonar-project.properties
INFO: Analyzing on SonarQube server 9.4.0
INFO: Default locale: "en_AU", source code encoding: "windows-1252" (analysis is platform dependent)
INFO: ------------------------------------------------------------------------
INFO: EXECUTION FAILURE
INFO: ------------------------------------------------------------------------
INFO: Total time: 0.405s
INFO: Final Memory: 3M/15M
##[error]ERROR: Error during SonarScanner execution
java.lang.UnsupportedClassVersionError: org/sonar/batch/bootstrapper/EnvironmentInformation has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
I had Java v11 installed on the Sonarcube server, but the error is saying its the Build Agent that doesn't have Java v11.
I decided to add the Java v12 bin path to the Environment Variable Path for it to be detected. IMPORTANT THIS NEEDS TO BE DONE ON THE BUILD AGENT:
For a Hosted Build Agent you can install JDK v11 or use this PowerShell script step:
- task: PowerShell#2
displayName: 'Download and Install Java v11'
inputs:
targetType: 'inline'
script: |
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$Command = "c:\jdk-11.0.15_windows-x64_bin.exe"
$Parms = "/s"
Write-Host [System.IO.File]::Exists($Command)
if ([System.IO.File]::Exists($Command)) {
Write-Host 'Downloading Java11.exe'
Invoke-WebRequest https://yourOwnUrl.com/jdk-11.0.15_windows-x64_bin.exe -OutFile $Command
}
Write-Host [System.IO.File]::Exists($Command)
& "$Command" $Prms
[System.Environment]::SetEnvironmentVariable("JAVA_HOME", "C:\Program Files\Java\jdk-11.0.15")
[System.Environment]::SetEnvironmentVariable("Path", [System.Environment]::GetEnvironmentVariable('Path', [System.EnvironmentVariableTarget]::Machine) + ";$($env:JAVA_HOME)\bin")
In my case, I'm building with VS2019 some C++ code that is using ANTLR4.
ANTLR4 is java based, and to use it I run java commands as a custom build step.
Earlier that day I had updated my JRE (Java Runtime Environment) on my new laptop to 1.8. Not thinking, since it's been a year since I ran ANTLR4 stuff... I need the full JDK to COMPILE with java. So I had a 1.8 RUNTIME, but the VS2019 build shell was finding the JDK1.7 compiler. Once I installed the 1.8 JDK, all was good.
So 80% of the time JRE is fine for me... it's just when I need the full JDK, DOH I need the full JDK.
In build.gradle(app) update as below: (Worked for me)
kotlinOptions {
jvmTarget = '1.8'
}
For me this problem was resolved by just installing older version of testng. Looks like It compiles with my Java 8
If you're using IntelliJ IDEA and having this error, try this.
1. Command + , (Open Preferences)
2. Build, Execution, Deployment > Build Tools > Gradle
3. Gradle JVM > Change it to a proper version
Check the version of Java configured in IDE by navigating to Settings -> Build, Execution, Deployment > Build Tools > Gradle
In my case, I use the IntellJ Idea and set JDK11 as my SDK and JDK17 in gradle setting.
Just update my SDK as JDK17, it was solved
Check the JDK in "Project Setting"(CMD+;) -> SDK
with
the gradle JVM in "Preference"(CMD+,) -> Build Tools -> gradle JVM
Faced the same issue when initialise my project from spring initizer
We need to match the version of java.sourceCompatibility and jvmTarget used for run and compile in "build.gradle.kt" file.
Last week, I updated my Mac's Android Studio from 2021.2.1 to 2021.3.1. Then our project was built failed for the similar reason:
Cause: com/android/tools/idea/gradle/run/OutputBuildAction has been
compiled by a more recent version of the Java Runtime (class file
version 55.0), this version of the Java Runtime only recognizes class
file versions up to 53.0
I found several discussion on the Jetbrains YouTrack Forum: Failed to run Android project in the Idea 2020.3 EAP (OutputBuildAction has been compiled by a more recent version of the Java Runtime (class file version 55.0)). The suggested workaround is to update the defined Gradle JDK version to JDK11, but many Android projects don't support Gradle JDK11, so does mine.
Another solution is to downgrade Android Studio from 2021.3.1 to 2021.2.1, and it worked for me. Hope it helps.
it looks like everyone is using windows for development, but if you use Linux, lower your Java version. maybe install JDK 8, the version table provided by #Nithin should give you an idea of which version you want to install.
After configuring the version of the compiler to 1.8 (your required version), try the older version of spring boot currently it is 3.0.0 by default but you can try 2.7.6 instead.
enter image description here
I need to see my dependencies in Gradle to fix a problem with multiple SLF4J bindings.
However, when I run 'gradle dependencies' I get the error:
Could not initialize class org.codehaus.groovy.runtime.InvokerHelper
In a similar question in stack-overflow Android Studio Could not initialize class org.codehaus.groovy.runtime.InvokerHelper
it was recommended to
install java jdk-14
upgrade to gradle version 6.3
I changed the jdk to 14 in IntelliJ in 2 places:
File -> Project Structure -> Project -> Project SDK
Preferences -> Gradle -> Gradle JVM
I attempted to update gradle from the command line with:
'gradle wrapper --gradle-version 6.3'
and got the same error:
Could not initialize class org.codehaus.groovy.runtime.InvokerHelper
I then changed the field 'distributionUrl' in the file 'gradle-wrapper.properties' to 'gradle-6.3', as instructed here https://github.com/gradle/gradle/issues/10248.
I tried various combinations of jdk and gradle versions but nothing seems to work.
So from your repo, if you have gradle-wrapper.properties like this:
➜ cat gradle/wrapper/gradle-wrapper.properties
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-6.3-bin.zip
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
On first compilation, Gradle tells you that:
build file '/Users/tim/Code/Java/brobotREST/build.gradle': 36:
all buildscript {} blocks must appear before any plugins {} blocks in the script
So if you move the buildscript section up to the top of the build.gradle file, it all seems to work
And I get:
➜ ./gradlew -version
------------------------------------------------------------
Gradle 6.3
------------------------------------------------------------
Build time: 2020-03-24 19:52:07 UTC
Revision: bacd40b727b0130eeac8855ae3f9fd9a0b207c60
Kotlin: 1.3.70
Groovy: 2.5.10
Ant: Apache Ant(TM) version 1.10.7 compiled on September 1 2019
JVM: 14 (Azul Systems, Inc. 14+36)
OS: Mac OS X 10.15.4 x86_64
I had a similar problem on macOS. It seems, it was a problem with version difference by IntelliJ IDEA and Gradle.
I adjusted the Gradle version in /gradle/gradle-wrapper.properties.
In my case I have set:
distributionUrl=https\://services.gradle.org/distributions/gradle-6.6.1-bin.zip
and now it works.
See also Gradle: Could not initialize class org.codehaus.groovy.runtime.InvokerHelper
Had a similar problem on Windows 10 caused by a java version issue.
In build.gradle set the java source compatibility flag; For java 1.8 this is
sourceCompatibility = '1.8'
then check the system version is the same
java -version
While running a script, I am getting the following error message in the Eclipse console:
Class has been compiled by a more recent version of the Java Environment (class file version 53.0), this version of the Java Runtime only recognizes class file versions up to 52.0.
Java Version: 8
IDE: Eclipse Oxygen
Firefox Version: 46
This is just a version mismatch. You have compiled your code using java version 9 and your current JRE is version 8. Try upgrading your JRE to 9.
49 = Java 5
50 = Java 6
51 = Java 7
52 = Java 8
53 = Java 9
54 = Java 10
55 = Java 11
56 = Java 12
57 = Java 13
58 = Java 14
59 = Java 15
60 = Java 16
61 = Java 17
62 = Java 18
63 = Java 19
IDE: Eclipse Oxygen.3
To temporarily correct the problem do the following:
Project menu > Properties > Java Compiler > Compiler compliance level > 1.8
A permanent fix likely involves installing JDK 9.
FYI 1.8 is what Java 8 is called.
Side bar
I recently returned to Java after a foray into C# (a breath of fresh air) and installed Eclipse Oxygen onto a clean system that had never had Java installed on it before. This default everything with a brand new install of Eclipse Oxygen yet somehow or other Eclipse can't get its own parameters to match the jdk that's installed. This is the second project I created and the second time I ran into this headache. Time to go back to C#?
Related Question
has been compiled by a more recent version of the Java Runtime (class file version 53.0)
You might see this error in IntelliJ as well and this comes up in Google.
I think it's a Gradle error more than an IDE error.
The fix (stolen from here) is configure Java 11 as a Gradle JVM in IntelliJ:
File -> Settings -> Build, Execution & Development -> Build Tools -> Gradle and change Gradle JVM to 11
That screenshot stolen from the Jetbrains issue as well
You can try this way
javac --release 8 yourClass.java
For Android Studio, File -> Project Structure [Ctrl + Alt + Shift + S]
53 stands for java-9, so it means that whatever class you have has been compiled with javac-9 and you try to run it with jre-8. Either re-compile that class with javac-8 or use the jre-9
For temporary solution just right click on Project => Properties => Java compiler => over there please select compiler compliance level 1.8 => .class compatibility 1.8 => source compatibility 1.8.
Then your code will start to execute on version 1.8.
I had a similar issue from the console after building a Jar in Intellij. Using the Java configuration to update to a newer version (Windows -> Configure Java -> Update -> Update Now) didn't work and stuck at version 1.8 (Java 8).
To switch to a more recent version locally I had to install the Java 15 JDK from https://www.oracle.com/uk/java/technologies/javase-jdk15-downloads.html and add that to my Java runtime environment settings.
The solution for me was doing what Andrei Kuznetsov said at https://youtrack.jetbrains.com/issue/IDEA-251407/Failed-to-run-Android-project-in-the-Idea-20203-EAP-OutputBuildAction-has-been-compiled-by-a-more-recent-version-of-the-Java, summarized in the following image:
"Root cause: IDEA sources are now compiled against Java 11. Known workaround is to configure Java 11 as a Gradle JVM." (Andrei Kuznetsov)
Your JDK version: Java 8
Your JRE version: Java 9
Here your JRE version is different than the JDK version that's the case. Here you can compile all the java classes using JDK version 1.8. If you want to compile only one java class just change the *.java into <yourclassname>.java
javac -source 1.8 -target 1.8 *.java
source: The version that your source code requires to compile.
target: The oldest JRE version you want to support.
I'm writing this because I found the other answers hard to understand.
Essentially your JRE is not updated and/or Eclipse is not configured to use the most recent JRE.
On Windows, go to Control Panel -> Programs -> Java -> update and proceed to update java
or if you don't have Java, go to Oracle's website and download the most recent JRE.
Once this is done, go into eclipse, and under the project view, right click on your project, select Java Build Path, double click on JRE System Library, then Select Workspace Default JRE 14.1.
If a recent version of Java doesn't show up here, it probably isn't installed. Check you JRE(NOT JDK) version and make sure it's recent. If it is, try restarting the computer then trying this again.
IDE : Eclipse 2021-09
This is caused because you have compiled the code with java version 9 and have java8 installed. You don't have to update to solve this issue.
Right click on project > properties > Java Compiler > untick-Enable
project specific settings > configure workspace settings > tick-Use
default compliance settings > Apply and Close.
Now your code should be executed properly.
I've reproduced on Windows 10 the similar issue in format like:
Error: LinkageError occurred while loading main class ...
java.lang.UnsupportedClassVersionError: com/.../ServiceApplication
has been compiled by a more recent version of the Java Runtime (class file version 62.0),
this version of the Java Runtime only recognizes class file versions up to 61.0
after upgrading the project from Java 17 to Java 18.
I had project settings regarding to Java 18:
Command line:
java version "18.0.1.1" 2022-04-22
Java(TM) SE Runtime Environment (build 18.0.1.1+2-6)
Java HotSpot(TM) 64-Bit Server VM (build 18.0.1.1+2-6, mixed mode, sharing)
Project Structure -> Project Settings -> Project:
Project Structure -> Project Settings -> Modules:
Project Structure -> Platform Settings -> SDKs:
And the reason of this issue was:
I forgot to specify the correct version for Run/Debug Configurations -> Build and run to Java 18 instead of Java 17:
As it was compiled with a newer Java version, but running on the older one.
If it's Maven-related issue, you can modify POM by specifying the -source and -target of the Java Compiler.
Additional helpful links:
Setting the Java Version in Maven
Consuming Jar Artifact of a Specific Java Version
Go to Project section, click on properties > then to Java compiler > check compiler compliance level is 1.8 , or there should be no yellow warning at bottom
Refreshing gradle dependencies works for me: Right click over the project -> Gradle -> Refresh Gradle Project.
You should check your Project Facets.
Project Properties > Project Facets
Change java version to the same version you are using. That work for me!
I faced this error in Intellij. Apparently, choosing java 1.8 as the project SDK doesn't affect the javac compiler that's used to build the project.
To change that, go to Settings -> Build, Execution, Deployment -> Compiler -> Java Compiler, and change Project bytecode version to 8.
If you're using IntelliJ IDEA and having this error, try this.
Command + , (Open Preferences)
Build, Execution, Deployment > Build Tools > Gradle
Gradle JVM > Change it to a proper version
This is getting as an example
if your computer running on an older version of java and the Neo4J is compiled on the latest version, please try to install the same version or upper to your computer.
I'm getting the same problem with Sonarqube
has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
Sonarqube with AzureDevOps error output:
INFO: SonarScanner 4.6.2.2472
INFO: Java 1.8.0_231 Oracle Corporation (32-bit)
INFO: Windows Server 2016 10.0 x86
INFO: User cache: C:\Windows\system32\config\systemprofile.sonar\cache
INFO: Scanner configuration file: C:\agent_a_work_tasks\SonarQubePrepare_15b84ca1-b62f-4a2a-a403-89b77a063157\5.4.0\classic-sonar-scanner-msbuild\sonar-scanner-4.6.2.2472\bin..\conf\sonar-scanner.properties
INFO: Project root configuration file: C:\agent_a_work\189.sonarqube\out\sonar-project.properties
INFO: Analyzing on SonarQube server 9.4.0
INFO: Default locale: "en_AU", source code encoding: "windows-1252" (analysis is platform dependent)
INFO: ------------------------------------------------------------------------
INFO: EXECUTION FAILURE
INFO: ------------------------------------------------------------------------
INFO: Total time: 0.405s
INFO: Final Memory: 3M/15M
##[error]ERROR: Error during SonarScanner execution
java.lang.UnsupportedClassVersionError: org/sonar/batch/bootstrapper/EnvironmentInformation has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
I had Java v11 installed on the Sonarcube server, but the error is saying its the Build Agent that doesn't have Java v11.
I decided to add the Java v12 bin path to the Environment Variable Path for it to be detected. IMPORTANT THIS NEEDS TO BE DONE ON THE BUILD AGENT:
For a Hosted Build Agent you can install JDK v11 or use this PowerShell script step:
- task: PowerShell#2
displayName: 'Download and Install Java v11'
inputs:
targetType: 'inline'
script: |
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$Command = "c:\jdk-11.0.15_windows-x64_bin.exe"
$Parms = "/s"
Write-Host [System.IO.File]::Exists($Command)
if ([System.IO.File]::Exists($Command)) {
Write-Host 'Downloading Java11.exe'
Invoke-WebRequest https://yourOwnUrl.com/jdk-11.0.15_windows-x64_bin.exe -OutFile $Command
}
Write-Host [System.IO.File]::Exists($Command)
& "$Command" $Prms
[System.Environment]::SetEnvironmentVariable("JAVA_HOME", "C:\Program Files\Java\jdk-11.0.15")
[System.Environment]::SetEnvironmentVariable("Path", [System.Environment]::GetEnvironmentVariable('Path', [System.EnvironmentVariableTarget]::Machine) + ";$($env:JAVA_HOME)\bin")
In my case, I'm building with VS2019 some C++ code that is using ANTLR4.
ANTLR4 is java based, and to use it I run java commands as a custom build step.
Earlier that day I had updated my JRE (Java Runtime Environment) on my new laptop to 1.8. Not thinking, since it's been a year since I ran ANTLR4 stuff... I need the full JDK to COMPILE with java. So I had a 1.8 RUNTIME, but the VS2019 build shell was finding the JDK1.7 compiler. Once I installed the 1.8 JDK, all was good.
So 80% of the time JRE is fine for me... it's just when I need the full JDK, DOH I need the full JDK.
In build.gradle(app) update as below: (Worked for me)
kotlinOptions {
jvmTarget = '1.8'
}
For me this problem was resolved by just installing older version of testng. Looks like It compiles with my Java 8
If you're using IntelliJ IDEA and having this error, try this.
1. Command + , (Open Preferences)
2. Build, Execution, Deployment > Build Tools > Gradle
3. Gradle JVM > Change it to a proper version
Check the version of Java configured in IDE by navigating to Settings -> Build, Execution, Deployment > Build Tools > Gradle
In my case, I use the IntellJ Idea and set JDK11 as my SDK and JDK17 in gradle setting.
Just update my SDK as JDK17, it was solved
Check the JDK in "Project Setting"(CMD+;) -> SDK
with
the gradle JVM in "Preference"(CMD+,) -> Build Tools -> gradle JVM
Faced the same issue when initialise my project from spring initizer
We need to match the version of java.sourceCompatibility and jvmTarget used for run and compile in "build.gradle.kt" file.
Last week, I updated my Mac's Android Studio from 2021.2.1 to 2021.3.1. Then our project was built failed for the similar reason:
Cause: com/android/tools/idea/gradle/run/OutputBuildAction has been
compiled by a more recent version of the Java Runtime (class file
version 55.0), this version of the Java Runtime only recognizes class
file versions up to 53.0
I found several discussion on the Jetbrains YouTrack Forum: Failed to run Android project in the Idea 2020.3 EAP (OutputBuildAction has been compiled by a more recent version of the Java Runtime (class file version 55.0)). The suggested workaround is to update the defined Gradle JDK version to JDK11, but many Android projects don't support Gradle JDK11, so does mine.
Another solution is to downgrade Android Studio from 2021.3.1 to 2021.2.1, and it worked for me. Hope it helps.
it looks like everyone is using windows for development, but if you use Linux, lower your Java version. maybe install JDK 8, the version table provided by #Nithin should give you an idea of which version you want to install.
After configuring the version of the compiler to 1.8 (your required version), try the older version of spring boot currently it is 3.0.0 by default but you can try 2.7.6 instead.
enter image description here
I have a gradle project that I am trying to build.
when I execute gradle clean build, it fails with the following error message
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':FacebookUpdateDependencies'.
> Could not resolve all dependencies for configuration ':compiler'.
> Could not resolve com.company.facebook:compiler:1.2+.
Required by:
::1.0
> Could not resolve com.company.facebook:compiler:1.2+.
> Failed to list versions for com.company.facebook:compiler.
> Unable to load Maven meta-data from http://mycompanynexus/compiler/maven-metadata.xml.
> Could not GET 'http://mycompanynexus/compiler/maven-metadata.xml'. Received status code 500 from server: Internal Server Error
However, when I tried
./gradlew clean build the build is successful.
why the build fails in the former and not the latter?
here is revelant portion of build.gradle
task wrapper(type: Wrapper) {
gradleVersion = '2.11'
}
EDIT
local$: gradle -v
------------------------------------------------------------
Gradle 2.13
------------------------------------------------------------
Build time: 2016-04-25 04:10:10 UTC
Build number: none
Revision: 3b427b1481e46232107303c90be7b05079b05b1c
Groovy: 2.4.4
Ant: Apache Ant(TM) version 1.9.6 compiled on June 29 2015
JVM: 1.7.0_79 (Oracle Corporation 24.79-b02)
OS: Mac OS X 10.11.1 x86_64
local$ ./gradlew -v
------------------------------------------------------------
Gradle 1.12
------------------------------------------------------------
Build time: 2014-04-29 09:24:31 UTC
Build number: none
Revision: a831fa866d46cbee94e61a09af15f9dd95987421
Groovy: 1.8.6
Ant: Apache Ant(TM) version 1.9.3 compiled on December 23 2013
Ivy: 2.2.0
JVM: 1.7.0_79 (Oracle Corporation 24.79-b02)
OS: Mac OS X 10.11.1 x86_64
I just noticed that the wrapper version is 1.12 and not 2.12. That is, there is a very large version difference between the wrapper and the installed version of gradle. There have probably been many incompatible changes to the different gradle plugins over the last 2 years, which may lead to the build problems you observe.
As already mentioned the gradle wrapper is a separate version of gradle that resides in the gradle/wrapper folder of your project. The wrapper is only built/updated, when executing the wrapper task in your project (gradle wrapper). That is your project's wrapper has not been updated for the last 2 years or has been created with the wrong version initially (1.12 instead of 2.11).
Given the above it's hard the tell what is actually causing the build to fail - apart from the incompatibilities between gradle 1.12 and 2.13. But this version mismatch is probably the root cause of your problem.
Most likely your project won't built anymore using the wrapper once you regenerated the wrapper with version 2.11 (the version mentioned in the build file), as 2.11 is likely to be incompatible to 1.12 as well...
This tells you that your Gradle version 2.11 will be used when gradlew command is invoked instead of the one installed on system. Always run gradlew command as it ensures your build is run against the gradle version it is supposed to, you are never required to install the correct version of gradle and really speeds up the build time.
Here is an excerpt from Gradle Wrapper definition:
Most tools require installation on your computer before you can use them. If the installation is easy, you may think that’s fine. But it can be an unnecessary burden on the users of the build. Equally importantly, will the user install the right version of the tool for the build? What if they’re building an old version of the software?
The Gradle Wrapper (henceforth referred to as the “Wrapper”) solves both these problems and is the preferred way of starting a Gradle build.
If a Gradle project has set up the Wrapper (and we recommend all projects do so), you can execute the build using one of the following commands from the root of the project:
./gradlew (on Unix-like platforms such as Linux and Mac OS X)
gradlew (on Windows using the gradlew.bat batch file)
Each Wrapper is tied to a specific version of Gradle, so when you first run one of the commands above for a given Gradle version, it will download the
corresponding Gradle distribution and use it to execute the build.
I have a java-maven project. I want to convert it to gradle so I did:
gradle init --type pom
And I got an error:
FAILURE: Could not determine which tasks to execute.
* What went wrong:
Task 'init' not found in root project 'my-project'.
* Try:
Run gradle tasks to get a list of available tasks.
BUILD FAILED
Total time: 1.78 secs
I have the last version of gradle:
$ gradle --version
------------------------------------------------------------
Gradle 1.4
------------------------------------------------------------
Gradle build time: Monday, September 9, 2013 8:44:25 PM UTC
Groovy: 1.8.6
Ant: Apache Ant(TM) version 1.9.3 compiled on April 8 2014
Ivy: non official version
JVM: 1.7.0_51 (Oracle Corporation 24.51-b03)
OS: Linux 3.13.0-24-generic amd64
Are you sure that you don't have a multi-project build? Specifically, be sure that you haven't already init a gradle project in the directory one level above.
I had the same problem on Debian. I installed gradle using apt-get. It installed version 1.5. (it was built in 2014)
Then I installed gradle manually, and now it works fine.
To complete mate00's answer... Let's say "my-project" is the sub-project that fails on init. If you have a multi-project build and you have the line include 'my-project' in the main project's settings.gradle file, it will throw this error.
The solution is to comment out include 'my-project' in the main projects settings.gradle, run the init command on my-project, and then uncomment that line.