Gradle plugin fails because of trailing commas in Kotlin

[covercash2 (Chris Overcash)]

This issue has come up at least twice before:

Support for Kotlin 1.4

I’d like too report this as well. The number classes with trailing commas is growing quickly in our codebase and parser just fails with Kotlin parser failure on it rendering the analysis unusable.

Trailing comma on Kotlin 1.4

Versions Used Sonarqube Community Edition Version 8.9 (build 43852) Kotlin 1.4.31 IntelliJ 2021.1.1 SonarLint Plugin 4.16.0.31683 What’s wrong When trailing comma exists at the end of scope, sonarlint show parsing error. This seems to be resolved from sonarqube 3.6 but still reproduced after upgrading to 3.9 commnunity edition. Sample Code When I inspect code like below… class MyComponent( circuitBreaker: CircuitBreaker, webClient: WebClient, // this line's comma ) { // ....…

It seems like the SonarQube server has been updated to support this compiler version, but the Gradle plugin is still failing with Unable to parse file: <source_file>. Parse error at position n:m on all files with trailing commas. I would like to be able to track this issue. Let me know if there is a workaround; otherwise, we’ll need to use a different tool set.

[Margarita_Nedzelska]

Hello @covercash2,

Thanks for your message.

As you might have noticed, the issue was fixed almost a year ago and all the threads, you’re mentioning here are already closed. So in general the trailing coma should be parsed correctly.

Could you please share with me a little bit more details?

• Which products do you use (SonarLint, SonarQube, SonarCloud)
• Which versions of these products do you use?
• Could you please show me the example of not working trailing come?
• Could you please share your Configuration of sonarqube plugin in gradle build script?
• Could you please share the log with me?

Regards,
Margarita