This page documents how to work with SonarQube in Eclipse for versions 3.2+. For versions prior to 3.2, browse this page.

Managing Existing Issues

When going through the source code, SonarQubein Eclipse will highlight the existing issues. The idea is that once you have read the code and understood it, the cost of fixing an issue is low.

Fixing an Issue

Browse the Sonar Issues view that displays the list of issues of the selected resource (project, file, etc.):

A double-click on an issue icon opens the source code editor and highlights the issue:

Reviewing an Issue (Remote)

Just like it's possible to review an issue through the web interface, you can review an issue directly in Eclipse:

Checking Code Prior to Commit

SonarQubein Eclipse provides the ability to show the quality of changed/modified code prior to pushing it to the SCM.

After running a local analysis, if new issues have been introduced (comparison made against the latest analysis on the SonarQube server), Eclipse will clearly highlight them: the icon is red and the line is highlighted. Moreover, every new issue is by default marked as an Error, meaning that it will also show up in the Eclipse Problems view, and the Package/Resource explorer will clearly show that your project has problems: