INFO: User cache: C:\Windows\system32\config\systemprofile.sonar\cache
INFO: Java 1.8.0_231 Oracle Corporation (32-bit) 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'm getting the same problem with Sonarqube Consuming Jar Artifact of a Specific Java Version.If it's Maven-related issue, you can modify POM by specifying the -source and -target of the Java Compiler. I forgot to specify the correct version for Run/ Debug Configurations -> Build and run to Java 18 instead of Java 17:Īs it was compiled with a newer Java version, but running on the older one. Project Structure -> Platform Settings -> SDKs:.Project Structure -> Project Settings -> Modules:.Project Structure -> Project Settings -> Project:.Java HotSpot(TM) 64-Bit Server VM (build 18.0.1.1+2-6, mixed mode, sharing) Java(TM) SE Runtime Environment (build 18.0.1.1+2-6) I had project settings regarding to Java 18: This version of the Java Runtime only recognizes class file versions up to 61.0Īfter upgrading the project from Java 17 to Java 18. Has been compiled by a more recent version of the Java Runtime (class file version 62.0), I've reproduced on Windows 10 the similar issue in format like: Error: LinkageError occurred while loading main class.
0 kommentar(er)
