Guillaume Toison

> Since we updated our Sonar to 10.5 our call to `./gradlew sonar` fails. We can solve the problem by using `-Dsonar.plugins.downloadOnlyRequired=false`. Its a Kotlin only project and maybe the...

For anyone else affected by the issue, it seems that the `sonar.plugins.downloadOnlyRequired` needs to be set on the server administration page **and** as an analyzer option.

Since SonarQube 10.5 the analyzer only downloads the plugins relevant to the languages detected in your project, unless is `sonar.plugins.downloadOnlyRequired` is set to false. For non java projects (e.g. kotlin)...

> so the correct fix requires the sonar-java plugin to add the kt file suffix? I doubt Sonarsource would change that in their built-in plugin: it is for java, not...

Hum, Sonarqube should activate the sonar-java plugin if it sees .java sources (unless they are filtered out?) Is that a multi-module project with some .java sources only in some modules?

There is a multi-module project built and analyzed as part of the integration tests in this project, it seems to work OK with Gradle so I'm not sure what might...

I've made a Pull Request with changes to hopefully solve this problem: in #1033 the plugin does not rely on the built-in sonar-java. So it should work even if Sonarqube...

Thanks a lot for trying out the fix @Munken I looked at the change a bit more carefully and realized I had duplicated part of the existing code, I'm making...

Sorry, it's mostly the lack of free time on my end. I wanted to properly test #1035 and also wanted to upgrade SpotBugs itself as we are wrapping up the...

Hello, Bonjour, The constructor `RuleMetadataLoader(String resourceFolder)` was removed in https://github.com/SonarSource/sonar-analyzer-commons/commit/6bc3a722b65a577bc0c9b5a7f523d9a5c5c60a17 Now you need to initialize it with the set of rules activated by default and a `SonarRuntime` (you can probably...