On this page
Knowing where to begin looking for information is the first step to reaching out for help. Many answers to commonly found problems can be found on the SonarLint channel of the Sonar Community Forum. See below for the basic steps to access the SonarLint logs when the analysis results are not what you expected.
- Open the Eclipse Console view.
- Open the SonarLint Console.
- Behind the double-gear dropdown menu in the Console view, enable Verbose output and Analysis logs.
- Reproduce the issue; for example, reopen the offending file.
Sometimes errors are not in the SonarLint console but could be directly in Eclipse error logs.
- Open Eclipse Error Log view: go to Eclipse > Window > Show view > Other... > General and select Error Log from the list
- Look for an error event related to SonarLint
- Open event details to get the stacktrace
No. Scanner properties you may have defined in the
pom.xml files (for example
sonar.projectBasedir) only make sense when modifying the SonarScanner in the command line. 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, the best way is to use Connected Mode and set the configuration in the SonarQube or SonarCloud UI.
© 2015-2023, SonarSource S.A, Switzerland. Except where otherwise noted, content in this space is licensed under the GNU Lesser General Public License, Version 3.0. SONARLINT is a trademark of SonarSource SA. All other trademarks and copyrights are the property of their respective owners. See SonarSource.com for everything you need to know about the Sonar Solution.