![]() ![]() ![]() Previously, they were relying on self-hosted Mercurial servers this project involved bringing all of the development team and their tooling over to Git as well as moving the community to GitHub. The ‘Skara’ project has been an impressive effort from the entire OpenJDK community led by the Java Platform Group at Oracle. Therefore it’s a massive honor that we now get to help the team building the future of the Java language. The JDK project is at the heart of the Java community and Java is one of the most popular languages for projects on GitHub. The communities migration effort, codenamed Project ‘Skara’, brought JDK 16 main-line development into GitHub. $Command = "c:\jdk-11.0.15_windows-圆4_bin.Earlier this month we were thrilled to welcome the OpenJDK Community to GitHub. IMPORTANT THIS NEEDS TO BE DONE ON THE BUILD AGENT:įor a Hosted Build Agent you can install JDK v11 or use this PowerShell script step: - task: 'Download and Install Java v11' I decided to add the Java v12 bin path to the Environment Variable Path for it to be detected. I had Java v11 installed on the Sonarcube server, but the error is saying its the Build Agent that doesn't have Java v11. : 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 #ERROR: Error during SonarScanner execution INFO: Default locale: "en_AU", source code encoding: "windows-1252" (analysis is platform dependent) INFO: Analyzing on SonarQube server 9.4.0 INFO: Project root configuration file: C:\agent_a_work\189.sonarqube\out\sonar-project.properties 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.\bin.\conf\sonar-scanner.properties 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |