> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-for-eclipse/using/scan-my-project.md).

# Scan my project

SonarQube for IDE, a core component of the [SonarQube solution](https://www.sonarsource.com/), 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 achieve high-quality code.

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 <a href="#first-steps" id="first-steps"></a>

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 **SonarQube** > **Analyze**. Analyzing **Changed files** is possible only at the project level.

Check the [Running an analysis](/sonarqube-for-eclipse/getting-started/running-an-analysis.md) page for more information about triggering and refining the analysis process.

## Scanning while in Connected Mode <a href="#scanning-while-in-connected-mode" id="scanning-while-in-connected-mode"></a>

When running in [Connected mode](/sonarqube-for-eclipse/connect-your-ide/connected-mode.md), SonarQube for Eclipse will sync with the SonarQube 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.

{% hint style="info" %}
When running in connected mode with SonarQube Server 10.4 or newer, **Won’t Fix** becomes **Accept**.
{% endhint %}

## Specify additional analyzer properties

It is possible to specify extra analyzer properties that will be used for analysis. To define those properties, open the **Eclipse** > **Settings...** to open the preferences window, then find the **SonarQube** > **Analyzer Properties** window and select **New\...** to add a new property.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-for-eclipse/using/scan-my-project.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.