-
Notifications
You must be signed in to change notification settings - Fork 153
Troubleshooting
-
Open the SonarLint tool window (
View
>Tool Windows
>SonarLint
). -
Enable
Verbose output
andAnalysis logs
options in the tool window settings. -
Find the logs in the
Log
tab of the tool window.
No. Scanner properties you may have defined in sonar-project.properties
, pom.xml
, ... (like sonar.sources
, sonar.projectBasedir
, ...) only make sense in the command line SonarScanner context.
SonarLint tries to use IDE metadata to avoid other configurations.
If you want to share some configuration between SonarScanners and SonarLint, like exclusions or some analyzer properties, it is best to use Connected Mode and set the configuration in the SonarQube or SonarCloud UI.
There is a dedicated channel where you can get help for SonarLint: https://community.sonarsource.com/c/help/sl/
Before creating a new topic, please check if your question has already been answered.
When creating a new topic, please describe your issue with a maximum of details. Please provide if possible:
- IDE flavor/version/OS. Example: IntelliJ Community Edition 2020.3 on MacOSX:
- SonarLint version:
- Are you using connected mode? Y/N:
- If you are using Connected Mode, what is the SonarQube server version (or say if it is SonarCloud):
- If you are using Connected Mode, what are the installed analyzers? You can easily get a list by opening
https://<SQ server>/api/plugins/installed
in a web browser: - The full stacktrace of the error. See previous section to enable verbose output: