cnescatlab / cnescatlab/sonar-icode-cnes-plugin
ICode Plugin Blocking the analysis of a maven project
- Dominant language
- Java
- Stars
- 21
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Hi Team,
I have recently installed Icode-cnes-plugin on sonarqube-7.9 enerprise edition. This was installed as a part of requirement where one of the user wanted to analyse *.sh files for his project. As a part of testing post any plugin installation, i ran a maven analysis for a sample project. The analysis for this maven project failed with the below error:
"**_Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.7.0.1746:sonar (default-cli) on project maven--test1: The plugin [icode] does not support Java 1.8.0_242: fr/cnes/sonar/plugins/icode/ICodePlugin 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 -> [Help 1]_**"
Why is icode-cnes plugin used for a maven project where we have java files?
I ran another analysis for a different project which uses flow plugin and it was successful without any errors.
Please look into and kindly advise accordingly.
Note: Java version on the Linux client machine is java-1.8 and java-11. Attached are the screenshots:


Contributor guide
Research direction
Start by reproducing the Maven analysis on SonarQube 7.9 with the i-Code CNES plugin and the Java 8 and Java 11 runtimes described in the report. Review the ICodePlugin loading path and the reported class-file version mismatch; done means establishing whether the plugin should load for this analysis and documenting or correcting the compatibility issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, shell
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100