# Requirements

Each IDE extension of SonarQube for IDE has its own requirements to work properly with the most recent releases.

## Overview <a href="#overview" id="overview"></a>

For SonarQube for Eclipse to work properly in the Eclipse IDE:

* Eclipse Platform Requirement: the minimal version of the Eclipse platform that SonarQube for Eclipse supports. If you are not familiar with Eclipse versioning scheme, see [here](https://en.wikipedia.org/wiki/Eclipse_\(software\)#Releases).
* JVM requirement: SonarQube for Eclipse requires the minimal version of the JVM that is used to [run Eclipse](https://wiki.eclipse.org/Eclipse.ini#Specifying_the_JVM). The use of older versions is possible as long as it complies with your version of Eclipse.
* Node.js requirement: Node.js is only required to enable JavaScript, TypeScript, and CSS analysis. See the [#js-ts-and-css](#js-ts-and-css "mention") article below for full details.
* SonarQube Server minimal requirement: only if using connected mode. Usually means that the next LTA is also supported.

| SonarQube for Eclipse version | Eclipse platform requirement | JVM requirement | Node.js requirement                                                                                                                                   | SonarQube Server min requirement (for connected mode)                                                                   |
| ----------------------------- | ---------------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| 11.17                         | 4.17+ (2020-09+)             | 11+             | <p>20.12+,<br>the <a href="https://nodejs.org/en/about/previous-releases#release-schedule">active LTS</a> version 22.11.0+ is recommended</p>         | <p>9.9<br>(the <a data-mention href="/spaces/LWhbesChsC4Yd1BbhHhS">/spaces/LWhbesChsC4Yd1BbhHhS</a> is recommended)</p> |
| 11.11 - 11.16                 | 4.17+ (2020-09+)             | 11+             | <p>18.20+, 20.12+,<br>the <a href="https://nodejs.org/en/about/previous-releases#release-schedule">active LTS</a> version 22.11.0+ is recommended</p> | <p>9.9<br>(the <a data-mention href="/spaces/LWhbesChsC4Yd1BbhHhS">/spaces/LWhbesChsC4Yd1BbhHhS</a> is recommended)</p> |
| 11.0 - 11.10                  | 4.17+ (2020-09+)             | 11+             | <p>18.18+<br>(20.9+, the <a href="https://nodejs.org/en/about/previous-releases#release-schedule">active LTS</a>, is recommended)</p>                 | <p>9.9<br>(the <a data-mention href="/spaces/LWhbesChsC4Yd1BbhHhS">/spaces/LWhbesChsC4Yd1BbhHhS</a> is recommended)</p> |
| 10.1+                         | 4.8+ (photon+)               | 11+             | <p>18.18+<br>(20.9+, the <a href="https://nodejs.org/en/about/previous-releases#release-schedule">active LTS</a>, is recommended)</p>                 | 9.9                                                                                                                     |
| 9.0+                          | 4.8+ (photon+)               | 11+             | <p>18+<br>(20, the <a href="https://nodejs.org/en/about/previous-releases#release-schedule">active LTS</a>, is recommended)</p>                       | 8.9                                                                                                                     |
| 7.6-8.1                       | 4.8+ (photon+)               | 11+             | <p><br></p><p>14.20+ (16+ or 18+ recommended)</p>                                                                                                     | 7.9+                                                                                                                    |
| 7.4                           | 4.8+ (photon+)               | 11+             | 12.22+                                                                                                                                                | 7.9+                                                                                                                    |
| 7.x                           | 4.8+ (photon+)               | 11+             | <p><br></p>                                                                                                                                           | 7.9+                                                                                                                    |
| 6.x                           | 4.6+ (Neon+)                 | 1.8+            | <p><br></p>                                                                                                                                           | 7.9+                                                                                                                    |

## Language-specific requirements <a href="#language-specific-requirements" id="language-specific-requirements"></a>

Some languages require the use of [Connected mode](/sonarqube-for-eclipse/connect-your-ide/connected-mode.md) to analyze. Please see the [Rules and languages](/sonarqube-for-eclipse/using/rules.md) page for more details. Some of the languages require you to be online to download the analyzer.

### C and C++ analysis <a href="#c-and-c-analysis" id="c-and-c-analysis"></a>

Analysis of C and C++ code in SonarQube for Eclipse requires a [C/C++ Development Tool](https://github.com/eclipse-cdt/) (CDT) ; you can check the [Eclipse Embedded CDT documentation](https://projects.eclipse.org/projects/iot.embed-cdt) for more details.

Note that you might need to build your C/C++ project successfully once in the IDE in order for CDT to configure everything properly and for SonarQube for IDE to pick up this configuration for the analysis.

For instructions on how to configure a C/C++ project project, refer to the [Eclipse CDT documentation](https://help.eclipse.org/latest/index.jsp?topic=%2Forg.eclipse.cdt.doc.user%2Fconcepts%2Fcdt_o_home.htm).

### COBOL <a href="#cobol" id="cobol"></a>

COBOL analysis requires a COBOL IDE based on the Eclipse platform such as the [IBM IDz](https://www.ibm.com/products/developer-for-zos) or [BMC](https://docs.bmc.com/docs/bctwb2010/perform-sonarlint-analysis-1068404170.html) IDEs. Note that recent versions of SonarQube for Eclipse and our analyzers require a JRE 11+ in order to run, and IBM IDz only supports JRE 11 starting from [version 16](https://www.ibm.com/docs/en/developer-for-zos/16.0).

* Check the IBM documentation for more information about [SonarLint integration with Developer for z Systems](https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/blog-entry1/2017/07/07/sonarlint-integration-with-developer-for-zsystems).
* Some additional information is available for setting up a SonarQube for Eclipse with your [BMC Compuware Topaz Workbench](https://devops.api.bmc.com/guidelines/ispw/ispw_projects.html#setting-up-usage-of-sonar-lint).

### Java and JSP <a href="#java-and-jsp" id="java-and-jsp"></a>

Analysis of Java code requires the Eclipse sub-project [Java development tools](https://www.eclipse.org/jdt/) (JDT). This includes a Java compiler, incremental builder, editors, wizards, content assist, and all the other features of a first-class Java IDE.

### JavaScript, TypeScript, and CSS <a href="#js-ts-and-css" id="js-ts-and-css"></a>

Node.js is required to enable JavaScript, TypeScript, and CSS analysis.

* When the [Eclipse Wild Web Developer](https://projects.eclipse.org/projects/tools.wildwebdeveloper) plug-in is installed in the IDE, SonarQube for Eclipse tries to leverage the plug-in’s bundled Node.js installation, if the requirements are met.
* If needed, you can manually set your Node.js executable. The [Running an analysis](/sonarqube-for-eclipse/getting-started/running-an-analysis.md#javascript-and-typescript-analysis) article gives more detail about setting a path to your Node.js.


---

# 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/requirements.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.