Hello, thank you for your feedback.
Indeed, binding Eclipse with SonarQube is not meant as a means to push analysis results to the server.
The way we recommend to use SonarQube together with SonarLint is:
- Use SonarLint in your IDE to get instant feedback about potential issues while you code
- Analyze your code frequently with a SonarQube scanner - e.g with a continuous integration solution - to extract trends and have a global evaluation of the code quality, including test coverage
The benefits of using SonarLint’s connected mode (a.k.a SonarQube/SonarCloud binding) are the following:
- Settings set on server side - quality profiles, custom analysis settings, quality gates - are shared with all members of your team
- Issues suppressed as “won’t fix” or “false positive” on the server won’t show up in SonarLint
- Some languages are only available in connected mode
- Optional notifications keep you informed of your project’s quality gate status