[
https://issues.apache.org/jira/browse/IGNITE-22775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Korotkov updated IGNITE-22775:
-------------------------------------
Priority: Minor (was: Major)
> Fix PR sonar checks in github actions
> -------------------------------------
>
> Key: IGNITE-22775
> URL: https://issues.apache.org/jira/browse/IGNITE-22775
> Project: Ignite
> Issue Type: Task
> Reporter: Sergey Korotkov
> Assignee: Sergey Korotkov
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently the PR sonar check fails with the following error:
> {noformat}
> Error: Failed to execute goal
> org.sonarsource.scanner.maven:sonar-maven-plugin:4.0.0.4121:sonar
> (default-cli) on project apache-ignite: Execution default-cli of goal
> org.sonarsource.scanner.maven:sonar-maven-plugin:4.0.0.4121:sonar failed: An
> API incompatibility was encountered while executing
> org.sonarsource.scanner.maven:sonar-maven-plugin:4.0.0.4121:sonar:
> java.lang.UnsupportedClassVersionError:
> org/sonar/batch/bootstrapper/EnvironmentInformation has been compiled by a
> more recent version of the Java Runtime (class file version 61.0), this
> version of the Java Runtime only recognizes class file versions up to 55.0
> {noformat}
> Looks like the sonar scanner needs to be run with JDK17 now but still can
> analyze code built with JDK11.
> See for example:
> the
> https://docs.sonarsource.com/sonarcloud/appendices/scanner-environment/#maven-gradle
> https://docs.sonarsource.com/sonarcloud/appendices/scanner-environment/#jenkins
> --
> So we probably can try to setup the JDK17 just the bofore the scanner run in
> github actions.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
