You can discover and update Kotlin-specific properties in Administration > General Settings > Languages > Kotlin.
Kotlin analysis and bytecode
If you are not using the SonarScanner for Gradle or SonarScanner for Maven, it is strongly recommended to provide the paths of all dependency binaries used by the project in order to improve the analysis accuracy. You can provide these using the
sonar.java.libraries property (note that this property is shared with the Java analyzer and as such has
java in its name). This is a list of comma-separated paths to files with third-party libraries (JAR or Zip files) used by your project. Wildcards can be used:
Note that if you use the SonarScanner for Gradle or SonarScanner for Maven to scan your code, these scanners will auto-detect the value for this property. Thus, you don't need to provide it.
Specifying the Kotlin source code version
You can explicitly define which Kotlin version the analyzer should analyze your code based on. Provide the desired version in the format
X.Y as value to the
sonar.kotlin.source.version property (e.g.
As of August 2022, the Kotlin analyzer supports multi-threaded parsing. This is an experimental feature and is disabled by default. You can enable it by providing an appropriate number of threads with the property key
- Importing external issues (AndroidLint, Detekt and Ktlint)
- Test coverage and execution (JaCoCo)
Check the issue tracker for this language.
© 2008-2023, SonarSource S.A, Switzerland. Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution-NonCommercial 3.0 United States License. SONARQUBE is a trademark of SonarSource SA. All other trademarks and copyrights are the property of their respective owners.