> 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/resources/previous-versions.md).

# Previous versions

Everything you need to know about installing and running previous versions of SonarQube for Eclipse.

Please remember that Sonar officially supports only the latest version of SonarQube for Eclipse.

## Installing previous versions <a href="#installing-previous-versions" id="installing-previous-versions"></a>

Installation of an earlier version is possible by downloading the appropriate asset from the [SonarQube for Eclipse repository](https://binaries.sonarsource.com/?prefix=SonarLint-for-Eclipse/releases/).

{% hint style="info" %}
To run previous versions of SonarQube for Eclipse, you must also install the required version of Java. Please see the [Requirements](/sonarqube-for-eclipse/getting-started/requirements.md) page to check which version of JVM is right for you.
{% endhint %}

When installing from the Eclipse Marketplace (see [Installation](/sonarqube-for-eclipse/getting-started/installation.md)), the newest available version for your version of Eclipse will be presented. Check the SonarQube for Eclipse [Requirements](/sonarqube-for-eclipse/getting-started/requirements.md) page for more details.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-for-eclipse/resources/previous-versions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.