# Installation

SonarQube for IDE can be installed directly from your IDE’s Marketplace. 

## Instructions <a href="#instructions" id="instructions"></a>

SonarQube for Eclipse is a plugin that can be installed in most Eclipse-based IDEs (including Spring Tool Suite, PyDev, and others). You can find the SonarQube for IDE extension directly on the [Eclipse Marketplace](https://marketplace.eclipse.org/content/sonarlint). All versions of SonarQube for Eclipse are available on the [Eclipse binaries](https://binaries.sonarsource.com/?prefix=SonarLint-for-Eclipse/releases/) page.

### Using the Eclipse Marketplace client <a href="#using-the-eclipse-marketplace-client" id="using-the-eclipse-marketplace-client"></a>

1\. In your Eclipse-based IDE, open the Marketplace client: **Help** > **Eclipse Marketplace**

<div align="left"><figure><img src="/files/R5FUxqCeG0MzFJVZJs4K" alt="Go to Help > Eclipse Marketplace... to install SonarQube for Eclipse directly from the IDE." width="188"><figcaption></figcaption></figure></div>

2\. Search for `sonarqube`, and select **Install**\*.\*

<div align="left"><figure><img src="/files/yPdmMXHlIKaqXvrsH4sB" alt="Install SonarQube for Eclipse in the Eclipse Marketplace by searching for SonarQube." width="563"><figcaption></figcaption></figure></div>

3\. Restart your IDE.

### Using the Eclipse Install New Software wizard <a href="#using-the-eclipseinstall-new-softwarewizard" id="using-the-eclipseinstall-new-softwarewizard"></a>

If you can’t use the Eclipse Marketplace client, you can still directly access the SonarQube for Eclipse update site. See the [official Eclipse documentation](https://help.eclipse.org/?topic=%2Forg.eclipse.platform.doc.user%2Ftasks%2Ftasks-124.htm) for full details, and follow these instructions:

1\. Go to **Eclipse** > **Help** and select **Install New Software**.

<div align="left"><figure><img src="/files/9QaMSmkhRYcH451eZ9p3" alt="Go to Help > Install New Software... in the Eclipse file menu to start your SonarQube for Eclipse installation." width="188"><figcaption></figcaption></figure></div>

2\. Select the **Add…** button to add a new repository pointing to `https://eclipse-uc.sonarlint.org`. Give the repository a meaningful name. Don’t worry if you, can’t open this URL in your web browser, Eclipse will automatically look for files [compositeContent.xml](https://eclipse-uc.sonarlint.org/compositeContent.xml) and [compositeArtifacts.xml](https://eclipse-uc.sonarlint.org/compositeArtifacts.xml).

<div align="left"><figure><img src="/files/CMqyOOd15c91dR3ilyQ8" alt="Add the SonarLint repository URL to the Location field in the Installation Wizard; this points to the SonarQube for Eclipse repository." width="375"><figcaption></figcaption></figure></div>

3\. Select both the newly added *SonarQube for Eclipse repository* and the **SonarLint for Eclipse** feature.

<div align="left"><figure><img src="/files/oxVU8PYYmcWnLdvy10Jg" alt="Select the SonarQube for Eclipse dependencies and packages to fit your application." width="563"><figcaption></figcaption></figure></div>

4\. Review the features about to be installed, and select **Finish**.

5\. When requested, restart your IDE.

{% hint style="info" %}
By using this method, you will be automatically notified of new updates of SonarQube for Eclipse (assuming you have allowed Eclipse to check for updates).
{% endhint %}

## First taste of SonarQube <a href="#first-taste-of-sonarlint" id="first-taste-of-sonarlint"></a>

Now that you have SonarQube for Eclipse installed, open or create a new project containing source files in a programming language that SonarQube for Eclipse can analyze out of the box: Java, PHP, Python, JavaScripts or HTML. See the [Rules and languages](/sonarqube-for-eclipse/using/rules.md) page for a full list of available languages.

For example in Java, you can copy-paste this code snippet, with a typical bug when copy-pasting `for` loops:

```java
package org.mycompany;

import java.util.logging.Level;
import java.util.logging.Logger;

public class Main {

  private static final Logger LOGGER = Logger.getLogger(Main.class.getName());

  public static void main(String[] args) {
    for (int left = 0; left < 10; left++) {
      for (int right = 0; right < 10; left++) {
        LOGGER.log(Level.INFO, "Pair: ({0},{1})", new Object[] {left, right});
      }
    }
  }

}
```

If you open this Java file within the Eclipse Java editor, you should see SonarQube for Eclipse reporting the issue:

<div align="left"><figure><img src="/files/PFyKiTyWRPNVvUBwIa6L" alt="SonarQube for Eclipse gives you squiggly lines and an Overview ruler mark in the sidebar to help call out issues in the Eclipse code explorer." width="563"><figcaption></figcaption></figure></div>

To get more details about the issue, you can simply hover on the issue location, and a popup will display the issue message:

<div align="left"><figure><img src="/files/MvfJGgbr4ecgUMFTKQj6" alt="Hover over an issue found by SonarQube for Eclipse to pull up a message and quick fix (when available)." width="375"><figcaption></figcaption></figure></div>

You can also use the SonarQube for Eclipse **On-The-Fly** view to display the list of issues found by SonarQube for Eclipse. Simply open the view from the menu **Windows** > **Show View** > **Other**.

<div align="left"><figure><img src="/files/hO47T2rMgPzyyYOnrrrJ" alt="To open a Sonarube view that isn&#x27;t showing, go to Windows > Show View > Other > SonarQube and choose your views. Here, we are opening the On-The-Fly view to see issues found in the open file." width="153"><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="/files/Q3FcU6ggbRZlPIdz31Zb" alt="The SonarQube On-The-Fly view shows you issues found in the active file." width="563"><figcaption></figcaption></figure></div>

## Preferences menu <a href="#preferences-menu" id="preferences-menu"></a>

Once your installation is complete, have a quick look at the SonarQube preferences menu. Navigate to **Window** > **Preferences** > **SonarQube** (or **Eclipse** > **Settings…** > **SonarQube** for Mac OS) for access to the **SonarQube Preferences** menu. Here you will find five menus to:

* Pass additional **Analyzer Properties** to the SonarQube for Eclipse analyzers. More information is available on the [Scan my project](/sonarqube-for-eclipse/using/scan-my-project.md) page.
* Add/remove **File Exclusions for** your analysis. See the [File exclusions](/sonarqube-for-eclipse/using/file-exclusions.md) for details.
* Agree/disagree to share anonymous telemetry statistics in the **Miscellaneous** menu.
* Access a list of **Release Notes**.
* And specifically define your **Rules Configuration** (when running in stand-alone mode). See [Rules and languages](/sonarqube-for-eclipse/using/rules.md#using-sonar-rules) for more information about how then work in SonarQube for Eclipse.

## Connect to your server <a href="#updating-sonarlint-in-vs-code" id="updating-sonarlint-in-vs-code"></a>

Connect SonarQube for VS Code to your instance of [SonarQube Server](/sonarqube-server/2026.1/user-guide/connected-mode.md), [SonarQube Cloud](/sonarqube-cloud/analyzing-source-code/connected-mode.md), or [SonarQube Community Build](/sonarqube-community-build/user-guide/connected-mode.md) to expand your analysis capabilities and share quality profiles with your team. See the article about connected mode [Connected mode](/sonarqube-for-eclipse/connect-your-ide/connected-mode.md#benefits), and the [Connected mode setup](/sonarqube-for-eclipse/connect-your-ide/setup.md) page for full instructions to get going.


---

# Agent Instructions: 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:

```
GET https://docs.sonarsource.com/sonarqube-for-eclipse/getting-started/installation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.