Data

Tools

Indexes

Applications

Experiments

Awesome

An open API service indexing awesome lists of open source software.

https://github.com/SonarSource/sonarlint-intellij

SonarLint for IntelliJ
https://github.com/SonarSource/sonarlint-intellij

intellij sonarlint

Last synced: about 2 months ago
JSON representation

SonarLint for IntelliJ

Awesome Lists containing this project

README 

        
SonarQube for IntelliJ Plugin

=========================



[![Build Status](https://api.cirrus-ci.com/github/SonarSource/sonarlint-intellij.svg?branch=master)](https://cirrus-ci.com/github/SonarSource/sonarlint-intellij)

[![Quality Gate](https://next.sonarqube.com/sonarqube/api/project_badges/measure?project=org.sonarsource.sonarlint.intellij%3Asonarlint-intellij&metric=alert_status)](https://next.sonarqube.com/sonarqube/dashboard?id=org.sonarsource.sonarlint.intellij%3Asonarlint-intellij)



SonarQube for IntelliJ is an IDE extension that supports you in writing [Clean Code](https://www.sonarsource.com/solutions/clean-code/), by

detecting and helping you fix quality issues as you type. See documentation details

for [Clean Code](https://docs.sonarsource.com/sonarlint/intellij/concepts/clean-code/).

Like a spell checker, SonarQube for IntelliJ squiggles flaws so they can be fixed before committing code.



Useful links

------------



- [Documentation](https://docs.sonarsource.com/sonarlint/intellij/)

    - A full list of supported programming languages and links to the static code analysis rules associated with each language are available

      on the [Rules page](https://docs.sonarsource.com/sonarlint/intellij/using-sonarlint/rules/).

- [Community](https://community.sonarsource.com/c/help/sl)

    - Report an issue, ask for some help, or suggest new features.



How to install

--------------



You can install SonarQube for IntelliJ from the [JetBrains Plugin Repository](https://plugins.jetbrains.com/plugin/7973-sonarlint), directly

available in the IDE preferences.



Full up-to-date details are available on the [Requirements](https://docs.sonarsource.com/sonarlint/intellij/getting-started/requirements/)

and [Installation](https://docs.sonarsource.com/sonarlint/intellij/getting-started/installation/) pages.



Questions and Feedback?

--------------------------



For SonarQube for IntelliJ support questions ("How do I?", "I got this error, why?", ...), please first read

the [FAQ](https://community.sonarsource.com/t/frequently-asked-questions/7204) to learn how to get your logs, and then head to

the [Sonar forum](https://community.sonarsource.com/c/help/sl). Before creating a new topic, please check if your question has already been

answered because there is a chance that someone has already had the same issue.



Be aware that this forum is a community, and the standard pleasantries are expected (_Hello, Thank you, I appreciate the reply, etc._). If

you don't get an answer to your thread, you should sit on your hands for at least three days before bumping it. Operators are not standing

by, but the Teams and Community Managers know that your questions are important. :-)



Contributing

------------



If you would like to see a new feature, check out the [PM for a Day](https://community.sonarsource.com/c/sl/pm-for-a-day-sl/41) page! There

we provide a forum to discuss your needs and offer you a chance to engage the Product Manager and development teams directly. Feel free to

add to an ongoing discussion or create a new thread if you have something new to bring up.



Please be aware that we are not actively looking for feature contributions. The truth is that it's extremely difficult for someone outside

SonarSource to comply with our roadmap and expectations. Therefore, we typically only accept minor cosmetic changes and typo fixes.



With that in mind, if you would like to submit a code contribution, please create a pull request for this repository. Please explain your

motives to contribute the change, describe what problem you are trying to fix, and tell us what improvement you are trying to make. The

SonarLint Team will review the PR and discuss internally how it aligns with

the [roadmap](https://www.sonarsource.com/products/sonarlint/roadmap/).



Make sure that you follow our [code style](https://github.com/SonarSource/sonar-developer-toolset#code-style-configuration-for-intellij) and

that all tests are passing.



How to build

------------



    ./gradlew buildPlugin



Note that the above won't run tests and checks. To do that too, run:



    ./gradlew check buildPlugin



For the complete list of tasks, see:



    ./gradlew tasks



For external contributors, the project should be guaranteed to build from any specific tag. During the development phase, some

unreleased dependencies not accessible to the public could be used, preventing you from building the project.



How to run UI tests

-------------------



    ./gradlew :its:runIdeForUiTests &



The above will start an IDE instance with the SonarQube for IntelliJ plugin. Wait for the UI robot server to start, then run the ITs:



    ./gradlew :its:check



Finally, close the IDE.



To test against a specific version of IntelliJ, the `ijVersion` property can be used, e.g.:



    ./gradlew :its:runIdeForUiTests  -PijVersion=IC-2019.3 &



To test against a specific IDE, the `runIdeDirectory` property can be used as such:



    ./gradlew :its:runIdeForUiTests -PrunIdeDirectory= &



Please note that the IDE must be in the foreground while tests are executed.



Because some ITs are leveraging SonarCloud, make sure the `SONARCLOUD_IT_TOKEN` env var is defined (you can find the value in our

password management tool).



How to debug UI tests

---------------------



If you want to debug what happens on the test side, you can simply launch the test in debug mode from the IDE.



If you want to debug what happens in the SonarQube for IntelliJ plugin, you can open the project in IntelliJ, and run the

`its:runIdeForUiTests` task in debug mode (for example from the Gradle panel on the right).



How to debug SLOOP

------------------



If you want to debug SLOOP:



* open the Run configuration you are using to launch the IDE (`runIde` or `its:runIdeForUiTests`)

* Add an environment variable: `SONARLINT_JVM_OPTS` with the value `-agentlib:jdwp=transport=dt_socket,address=8080,server=y,suspend=n`

* Run the task

* Open the SLCORE project and click `Run` > `Attach to process`

* Choose the SLOOP running process



If you want to plug the debugger as soon as SLOOP is started, you can modify the command above by having `suspend=y`.

This will wait for the debugger to attach the process before starting SLOOP.



How to develop in IntelliJ

--------------------------



Import the project as a Gradle project.



Note: whenever you change a Gradle setting (for example in `build.gradle.kts`),

don't forget to **Refresh all Gradle projects** in the **Gradle** toolbar.



To run an IntelliJ instance with the plugin installed, execute the Gradle task `runIde` using the command line,

or the **Gradle** toolbar in IntelliJ, under `Tasks/intellij`.

The instance files are stored under `build/idea-sandbox`.



To run against a specific IDE, the `runIdeDirectory` property can be used as such:



    ./gradlew :runIde -PrunIdeDirectory=



Keep in mind that the `clean` task will wipe out the content of `build/idea-sandbox`,

so you will need to repeat some setup steps for that instance, such as configuring the JDK.



Whenever you change the dependency version, the previous versions are not deleted from the sandbox, and the JVM might not load the version

that you expect.

As the `clean` task may be inconvenient, an easier workaround is to delete the jars in the sandbox, for example with:



    find build/idea-sandbox/ -name '*.jar' -delete



License

-------



Copyright 2015-2025 SonarSource.



Licensed under the [GNU Lesser General Public License, Version 3.0](http://www.gnu.org/licenses/lgpl.txt)