We having a gradle kotlin based project and a default SonarQube Community Edition. We are using the latest version (4.4.1.3373) of the sonarqube-gradle-plugin. We also using a custom Gradle distribution where we define repositories,
When we execute the sonar Gradle task on our project, we see the exception. With our previous SonarQube version (9.9) we did not have this issue.
We tried setting the sonar.kotlin.file.suffixes to not .kt and .kts, which fixes the error, but we loose scan results of our Kotlin files.
Thanks for the report. This is happening when we try to analyze your build.gradle.kts and settings.gradle.kts files. Could you please exclude them from the analysis and check if everything works again?
This was fine in 9.9 because we recently introduced the analysis of your build scripts.
Meanwhile, we will try to investigate and fix the issue. You can track it here: [SONARKT-370] - Jira
Yes, 10.3 was released before we delivered a fix (The fix should have been done in sonar-kotlin-plugin). So I think once 10.4 is out, your issue will be fixed, meanwhile using plugin for Gradle 4.2 could be your workaround.