I've recently installed Sonar 4.5.1 with Sonar Runner 2.4, Issue report plugin 1.0.
It reports error when running the analysis:
ERROR: Error during Sonar runner execution
ERROR: Unable to execute Sonar
ERROR: Caused by: Fail to generate HTML Issues Report to: /home/.sonar/issues-report.html
ERROR: Caused by: ruleStatus.getRule().getId() is undefined.
ERROR:
ERROR: To see the full stack trace of the errors, re-run SonarQube Runner with the -e switch.
ERROR: Re-run SonarQube Runner using the -X switch to enable full debug logging.
Build step 'Invoke Standalone Sonar Analysis' marked build as failure
Can anyone help?
Thanks in advance,
Upgrading to Issue report plugin 1.3 solved the problem.
Related
Task :compileJava FAILED
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':compileJava'.
error: invalid source release: 17
I have spent more than 5-6 hours fixing this issue. Due to this i am not able to run my application. Please help me out so that i can proceed
update: I am able to create build successfully in eclipse. but now it is failing with error
Error: Could not find or load main class com.abc.ABCServiceApp
Caused by: java.lang.ClassNotFoundException: com.abc.ABCServiceApp
and build is still failing through terminal with the same error
C:\Users\user\Documents\abc\def\xyzservice>gradle build
Task :compileJava FAILED
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':compileJava'.
error: invalid source release: 17
Try:
Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.3.3/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 3s
3 actionable tasks: 1 executed, 2 up-to-date
Update: i want to run this project usinh openJDK-15
C:\Users\user1>java -version
openjdk version "15" 2020-09-15
OpenJDK Runtime Environment (build 15+36-1562)
OpenJDK 64-Bit Server VM (build 15+36-1562, mixed mode, sharing)
Update:
i think below is the problem. i want to run my application with java 15, but it is set to java 17, i tried changing it back to 15, but it again get set to 17
Update: lost my patience. Installed another eclipse and it workimg now
It was a IDE issue, somehow it was picking Java17 even though after setting it to 15. Thank you all for your reply. It helped at least to know the root cause. I uninstalled the eclipse and re-installed a fresh one. It works now
Ha anyone else run into an issue when connecting the SonarLint plugin, version 3.2.0, to a SonarQube 6.2 server where the following error is thrown:
java.lang.NoClassDefFoundError: com/villagechief/sonar/salesforce/core/ApexCodeColorizer
I connected the plugin to the SonarQube server in order to bind the project. It looks like the rules where pulled properly, but when I click on 'Analyze' or 'Analyze changed files', the error above is thrown.
These are my properties being passed:
extraProperties: {sonar.java.source=1.8, sonar.java.target=1.8, sonar.libraries=/Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home}
I recently upgraded my Sonar Version to 5.5 and all the compatible plugins with it.
Here are the versions of the plugins installed:-
sonar-ldap-plugin-1.5.1.jar
sonar-javascript-plugin-2.13.jar
sonar-java-plugin-3.14.jar
sonar-build-breaker-plugin-2.1.jar
sonar-php-plugin-2.8.jar
sonar-findbugs-plugin-3.3.jar
If I use sonar-findbugs-plugin-3.3.jar, the Sonar is not getting Up and throwing below error :-
java.lang.IllegalArgumentException: The rule 'EC_INCOMPATIBLE_ARRAY_COMPARE' of repository 'findbugs' is declared several times
If I downgrade the Jar to sonar-findbugs-plugin-3.2.jar it works but fails to analyse the Project and throws below error :-
An API incompatibility was encountered while executing org.sonarsource.scanner.maven:sonar-maven-plugin:3.0.2:sonar
I have tried the versions - 3.3,3.3.1 and 3.3.2
Any Help ?
I am using STS 3.6.0 and during STS startup I am getting error:
org.eclipse.osgi.internal.framework.EquinoxConfiguration$1
Could not fetch model of type 'EclipseProject' using Gradle installation 'C:\build-tools\gradle-1.10'.
And I can't run Gradle task for the project. Any suggestion?
The error message looks similar to the error in this bug [1].
This bug is actually caused by a bug in Eclipse 4.4.2 [2]. There are a few things you can do to avoid this bug:
You can try a more recent version of gradle tooling (and/or STS)
install the workaround from eclipse update site as explained in comment 51 [3] of the Eclipse bug
[1] https://issuetracker.springsource.com/browse/STS-3922
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122#c51
I'm using a eclipse 4.2 distribution and have installed the gradle eclipse integration plugin from springsource.
When I initially try to create a quick java project with the wizard I get the following error:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at C:\devtools\gradle-1.4\docs\userguide\gradle_daemon.html
Please read below process output to find out more:
-----------------------
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Could not fetch model of type 'HierarchicalEclipseProject' using Gradle installation 'C:\devtools\gradle-1.4'.
When I run gradle build in the command line everything's fine.
Any ideas how i could get this to work?
Cheers
Since you can run gradle in command line successfully, you would want to try to use that gradle in the eclipse plugin.
Set Preference -> Gradle -> Gradle Distribution -> Folder to your own gradle distribution that runs fine.