When I run ./gradlew sonarlintMain, it correctly excludes the rule. However, in IntelliJ IDE, any new user who onboards to this project will have this rule visible as an issue. Also, if they ever configure a local exclusion, they may have an unintentional mismatch vs. this project shared configuration, which they won’t be informed about.
One recommendation would be for an option to manually import a list of rules, but I’m also asking you to recognize such an officially supported Gradle plugin and use its exclusion rules automatically by default, unless user specifies otherwise.
Thanks for reaching out. There is no configuration done on the official SonarLint for IntelliJ plug-in (phrasing it, especially this way) as it is not linked at all to the Gradle plug-in you’re mentioning that is not official (despite what you mentioned), which is created by a community member.
As such, we don’t support this Gradle plug-in, including honoring its configurations, and we also won’t do so, at least not in the near future as this is not officially our product. For your first request, I invite you to leave your feedback on our roadmap!
On the other hand, the best option to enforce the same ruleset and do collaborative work, including new users, is to use the Connected Mode with either SonarQube (this is self-hosted, therefore I would also recommend to you) or SonarCloud (our cloud-based collaboration tool) that is working seamlessly with SonarLint.
I don’t have account at sonarsource.productboard.com. In any case, please consider becoming an official partner of your “only Gradle plugin”, I’m sure it won’t be so difficult to read the configuration or ask the developer for some integration. Or if sonar-project.properties project file allows sharing this ruleset, maybe that file could be used for the sync. (And personally I had issues setting up the IntelliJ plugin to use SonarQube, which is also less lightweight.)
Thanks for reaching out.
I understand your point about rule exclusion, especially when you work as a team, and you want to share the same configuration.
I will track your insight to potential improvement in the future. Note that it is not planned in the short term because we have other priorities.