Scan my project
On this page
SonarQube for IDE, a core component of the Sonar solution, is a developer's first line of defense to find and fix coding issues in real-time. The results of a SonarQube for IDE scan provide rich contextual guidance to help you improve your skills while enhancing productivity to help you resolve issues in code.
SonarQube for IDE scans your project to provide instant feedback against hundreds of language-specific rules. When running in connected mode with SonarQube Server or SonarQube Cloud, you can benefit from additional rules that identify security vulnerabilities and security hotspots as well as take advantage of team features that help your organization work towards a Clean Code state.
Every organization has custom policies and procedures; the SonarQube for IDE analyzer offers a level of customization to help you achieve those practices.
First steps
By default, SonarQube for Eclipse will automatically analyze all open files. In addition, scanning a full project including unopened files, or scanning all changed files is possible.
Right-click on a file, multiple files, or on the project folder in the Eclipse Explorer and select SonarLint > Analyze. Analyzing Changed files is possible only at the project level.
Check the Running an analysis page for more information about triggering and refining the analysis process.
Scanning while in Connected Mode
When running in Connected Mode, SonarQube for Eclipse will sync with the SonarQube (Server, Cloud) Quality Profile to download issues and suppress those marked as safe or won’t fix on the server. The analyzer properties and rules will be respected, and SonarQube for Eclipse will use locally what is defined on the server.
When running in connected mode with SonarQube 10.4 or newer, Won’t Fix becomes Accept.
Was this page helpful?