-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java:s4143 not found in sonarqube 7.9.4 #111
Comments
Thanks for finding this bug. |
This is an issue related to the version of SonarJava that is installed on the server. Not all rules that we are using are available in all versions of SonarJava. I am working on a fix for this right now, so that we can include / exclude certain rules by detecting which version of SonarJava is running on SonarQube. |
I am totally new to sonarqube plugin creations, but if you need a logic which will work in any environment, possibly you can enable any of the dependent rules just in case they are available at all? |
As we are adding the rules to our quality profile sequentially, we should simply check if that rule is actually available and otherwise only log a warning and continue. If no other way, we can simply catch the exception and proceed. Even better would be to check the existance of the rule without exception if possible. |
As discussed with @lmarniazman the exception is not raised, when we are looking up or adding the rule but deferred after our plugin bootstrapping is completed. Therefore we can not catch the error and handle the problem. |
Expected behavior
As an architect, I want to install devon4j sonar plugin so that I can verify my architecture.
Actual behavior
After installing the latest sonar-devon4j-plugin from marketplace in sonarqube 7.9.4, I get the following blocking error on startup:
Steps to reproduce (bug) / Use Case of feature request (enhancement)
Related/Dependent Issues
Comments/Hints:
Further installed plugins:
![image](https://user-images.githubusercontent.com/1427255/97530626-d0a0bc00-19b2-11eb-9009-75dc987db861.png)
Affected version:
The text was updated successfully, but these errors were encountered: