[Intellij Sonarlint plugin] Respect pom.xml configurations

[gitgdako]

There are multiple configs in Mavens pom.xml that change the behaviour of a run for Sonarqube. These configurations should be used by the Sonarlint plugin as well

For example sonar.issue.ignore.multicriteria.* is not used, so Sonarlint shows issues that Sonarqube will not, because of the given configuration

This has not been a feature so far, so any Sonarlint and IntelliJ Version is affected

There are alternative ways to configure that in the Sonarlint plugin, in Sonarqube etc., but all of them need to be duplicated and maintained seperately. Using the link to Sonarqube is not practical as we can not guarantee up to date information to be available there as well as the synchronisation taking too long, both because our project is quite big

This topic has several duplicates [0] but none of them are as general and lack some information, I tried to be as general as possible. If I should move this to an issue tracker as a feature request with more information please point me in the right direction.

Edit: Like an idiot I have managed to duplicate my own issue from a year ago, which I have also linked below.

[0]

Sonarlint running locally does not catch parent pom.xml rule exclusion

Hi @NathanEckert SonarLint and SonarCloud analysis configurations follow a different approach. SonarCloud uses one of the SonarScanners (here I guess you are using the scanner for Maven). The scanner for Maven will try to infer your project structure from the Maven model. For special cases like yours, you can override the scanner behavior using properties sonar.sources and sonar.tests. SonarLint on its side relies on IDE metadata. IDEs like IntelliJ already have their own way to “understand” M…

SonarLint project configuration options

Operating system: W11 SonarLint plugin version: 10.2.1.77304 Programming language you’re coding in: Java/TS Is connected mode used: No We want to disable rule/file pattern combination for both SonarQube Enterprise as well as SonarLint for IntelliJ in a single place which is VCS tracked. The easy answer is to connect the plugin and configure in SonarQube. We would much rather have the project specification configuration as part of the VCS tracked project files. Furthermore access to the SonarQ…

[kussberg (Edgar)]

Hello, thanks so much for reaching out and providing such a clear, detailed description of the issue. I understand the frustration of having to duplicate configuration settings between your Maven pom.xml and the SonarLint plugin. What you describe is the key difference between SonarQube & SonarQube in IDE scan.

• SonarQube Scanner is built to parse your project’s pom.xml and directly apply properties like sonar.issue.ignore.multicriteria.*. It acts as a dedicated scanner that fully understands Maven’s project structure on the side of SonarQube Cloud/Server.

• SonarQube for IDE Scanner: is designed to use the IDE’s existing project configuration, not to parse external files for specific SonarQube properties. This is intentional; it ensures that IDE analysis aligns perfectly with what the developer “sees” and uses, such as the Java version, classpath, and dependencies.

This architectural difference is why IDE doesn’t automatically pick up the custom properties from your pom.xml, leading to different results. While I know neither of these options might be ideal for your large project, here are the current ways to get a consistent configuration:

1. Connected Mode (preferred): The most robust way to get a consistent analysis is by using SonarLint’s connected mode. When connected to a SonarQube instance, IDE extension will automatically download and apply the server’s configuration, including any issue exclusion rules. We get that you’re concerned about sync time for a large project and prefer not to manage properties on the server, but this is currently the designed path for keeping things in sync.

2. Standalone Mode / Manual Configuration: If you’re not using connected mode, you can manually set these properties within the IDE plugin settings in IntelliJ. There’s a dedicated property section where you can add the same sonar.issue.ignore.multicriteria.* properties from your pom.xml.

Let us know if that works for you. We really appreciate you taking the time for sharing this feedback with us!