Different binding per module in SonarLint IntelliJ

The Sonarlint Eclipse plugin allows to assign a separate binding for each module group inside an Eclipse project.
With the IntelliJ plugin I only can assign one binding to the complete project, but the project consists of multiple git repositories containing each separate maven module groups with separate sonar projects.

Hi there,

Can you clarify why you’re not analysing one git repo as one SonarQube project ? That’s the standard expectation for a bunch of reasons (not just SonarQube-related, but also in terms of overall CI/CD integration).

Not doing this is likely what prompts your need on the SonarLint side, but for now I see that as a collateral of the root-cause here: the unusual analysis approach (multiple SQ projects within one Git repo) you have in place.

No we use one SonarQube project for each git repo, but have multiple git repos inside one IntelliJ Project

The problem is related to difference between workspaces in Eclipse and IntelliJ. Eclipse workspace allows storing multiple projects and the same time. IntelliJ treats workspace as a one project and allows importing modules. Many developers don’t want to open one IntelliJ instance per project so they import projects as modules.

In my company we have excacly the same problem and we also want to report this idea :smile:

We have the exact same need: One Intellij project with modules that map to Git repos. Each module maps to a Sonarqube project.

1 Like

This is something that keeps me away from using Idea since i’m obsessed with SonarLint :slight_smile:. I think what we need here is the binding support for modules found in the Intellij Project similar to VCS roots configuration in IntelliJ when there are multiple VCS roots found. But i do agree that the plugin design has been done to align the intended usage of the IDE :slight_smile: even though the intended usage is not practical.

Hi,

On our side we have the exact same need as well.

@NicoB any update on this request ?

We have a gradle multi-module Project with different Subversion roots as well and would love to be able to configure the sonarqube project of each module individually as well with SonarLint.

1 Like

Looking forward to this feature!

We have exact same issue. Please add this feature to intellij plugin.

Hello, I’m currently facing the same issue :frowning:

Does anyone have any update on this issue?

Hi folks,

Thanks you all for the feedback. For the record this is the associated ticket in our backlog: https://jira.sonarsource.com/browse/SLI-171
Due to the number of votes/feedback on this thread, I will discuss this feature with the team, and we will let you know of the progress.

2 Likes

@Julien_HENRY what’s the current status?

This topic has not been prioritized on our side. Module-level services have recently been deprecated on Jetbrains plugin API side, so it will make the implementation of this feature even more complex. We would have to store at the project level the binding of each modules. I’m not sure it will fit the use case reported above (using IntelliJ project as a “workspace” and adding modules for each Git repositories), since the binding metadata will still be persisted at the project level, preventing to store it in each individual Git repository.

It would still be better than current solution :slight_smile:

FYI, this is also an issue in visual studio. We have the exact same use case and problem. One solution might contain 200 projects, but only one can be configured for sonarlint plugin at a time.

Any update on this Julien ?

From Webstorm 2019.2 - multiple projects can be opened in the same Webstorm instance.
I am not sure if other JetBrains IDEs do the same at this time.

File -> Open -> {browse to project} -> Open -> press “Attach” button.

SonarLint is just reporting 0 issues. For one of my colleagues it logs an error with message tsconfig.json not found.

We would like to adopt SonarLint at my organisation, but the multiple-project setup is widely used…