Message-ID: <47140960.2501.1418961628471.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2500_1881174441.1418961628470" ------=_Part_2500_1881174441.1418961628470 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
While browsing the source code, SonarQube in Eclipse highlights issues.&= nbsp;But its added value is to be able highlight the new issues that you ha= ve introduced while adding/modifying the source code. You can thus check yo= ur code prior to pushing it to the SCM to make sure that you haven't introd= uced any new issues.
To run a new analysis, right click on your project and go to Son= arQube > Analyze. You can also hit Ctrl+Alt+Q = wherever you are in your project to trigger a new analysis.
By default, the analysis mode is incr= emental. Because only new/modified files are checked, you get feedback = and the list of new issues very quickly.
Note that you can also run an analysis on a working set. This allows you= to trigger several analyses at once on all the projects of the working set= .
Parameters are retrieved as defined below:
There are two ways to know when the last analysis was run on a project:<= /p>
Four different views are available to browse the quality of your project= s:
The SonarQube Issues view displays the list o= f issues of the selected component (project, module, file, etc.). = ;To display this view, go to Window > Show View > Other.= .. > SonarQube > SonarQube Issues. Problems and Markers views also display issues= .
Issues are flagged in the source code viewer. New issues (compared to th= e latest version on the SonarQube server) are highlighted in yellow. This a= llows you to focus on the new issues that you have introduced.
You can add/remove/order columns, group issues (by severity, new issues = only, ...), filter issues (new issues only, issues assigned to me, ...), so= rt (by assignee, ...).
Note that "Resolved" issues are not displayed.
This view allows you to review the selected issue (add comments, confirm= it, plan it, etc.) the same way you would do it through the web interface.= To display this view, go to Window > Show View > O= ther... > SonarQube > SonarQube Issue Editor.
Note that it is not possible to review new issue that you have introduce= d.
This view allows you to access the detailed description of the coding ru= le of the selected issue. To display this view, go to Window &= gt; Show View > Other... > SonarQube > SonarQube Rule Description<= /strong>.
This view allows you to access the SonarQube web interface. This vi= ew is automatically displayed when clicking on SonarQube > = Open in SonarQube server. It can also be displayed by going to&nbs= p;Window > Show View > Other... > Sonar > Sonar Web Bro= wser.
It happens when the source folders= are not properly set in Eclipse.
Let's take the C/C++ project samp= le for instance. When you import it into Eclipse, by default the source= folder is set to /cpp-sonar-runner (and not to /cpp-sona= r-runner/src):
Therefore, SonarQube will try to retrieve data from files whose fully qu= alified names are src/BiggestUnInt.cc, src/HelloWorld.cpp= , etc. It will find none as the fully qualified names in SonarQube are = BiggestUnInt.cc, HelloWorld.cpp, etc. (without "src/&quo= t;):
Hence, you won't get any issue displayed in remote mode in Eclipse.
But if you set the source folder to cpp-sonar-runner/src instea= d:
you will get issues displayed: