- Sonarqube 7.3
- Sonarlint Eclipse 3.6.0
Analyzed project is organized with maven multi-module, like this :
ModuleA is a frontend module which is opened with WebStorm
ModuleB is a backend module which is opened with Eclipse
On Sonarqube we have configured few entries on “Ignore Issues on Multiple Criteria” on the root project (because this is the only place this kind of configuration can be put, cannot be done on a sub-project).
These configuration entries discard some rules on some java packages into ModuleB.
This works well on Sonarqube, but there is a problem with Sonarlint :
If we bind the Eclipse ModuleB project to “org-key:root”, rules are well discarded and not reported by sonarlint, following the multiple criteria entries, BUT any “Resolved” issues (won’t fix, false positive, …) are still reported wrongly
If we bind the Eclipse ModuleB project to “org-key:moduleB”, rule discarding from multiple criteria entries does not work anymore and issues are reported wronly, BUT this time all “Resolved” issues disappear correctly !
To solve this problem, we think that each sub-project should inherit all the root project configuration before applying specific sub-project configuration (overriding or not) and so allow the binding to be on sub-project.
Currently it is very annoying to choose between “let sonarlint report all discarded rules” or “let sonarlint report all resolved issues” …