Unwanted SonarLintModuleSettings added to module *.iml files

SonarQube for IDE IntelliJ Platform
1

Please provide

  • Operating system: windows 10
  • SonarLint plugin version: 8.5.1.75093
  • Programming language you’re coding in: Java
  • Is connected mode used: yes, but disconnecting does not solve the problem
    • Connected to SonarCloud or SonarQube (and which version): * Community Edition
      Version 8.9.10 (build 61524)

And a thorough description of the problem / question:

I suppose since the last update of the SonarLint plugin, or since i tried connecting sonarqube using a token instead of my login this behaviour started.

To each of the *.iml module config file a section is suddenly written:

<component name="SonarLintModuleSettings">
    <option name="uniqueId" value="40e9a5d8-3707-4f2a-9152-1e28fcc9944e" />
</component>

Disabling the SonarQube connection and restarting the IDE (latest Intellij Idea) does not resolve the problem.

This affects a LOT of files that are shared with a LOT of developers and we definitely do NOT want to commit this in SVN, if this cannot be fixed I think I will need to stop using SonarLint…

3 Likes
4

I have to agree here. The plugin writing to this file needs to be configurable. Especially if the IDE isn’t connected to the backend service. What about adding it to another file within the .idea folder?

We’ve rolled back to 8.4 for now.

1 Like
5

Hello guys,

Sorry for the late response. We introduced this change in a recent version (8.5) without thinking about this consequence. We understand it is annoying so we will change that for the next release (ticket). In the meantime, you can indeed downgrade to version 8.4 from the Marketplace.

Sorry for the inconvenience and thanks for raising this

2 Likes
9

Hey Damien,

Any luck with this one? It looked it was originally slated for 10.1 then 10.2 but still hasn’t been fixed.

Thanks!

1 Like
10

Hi @jcarty,

Unfortunately, we had other higher-priority topics in the last few months. We still plan to fix it, but it won’t realistically happen before Q1 2024. Sorry for the inconvenience

11

Hi, any update on this issue? I checked the atlassian issue you linked, but looks like it’s still in todo.
Best regards,
ML

14

Hello @Angelthree95,

Unfortunately, still no update to provide, we’ve been busy with other more important topics. It’s still on our radar, I just don’t know when we will get to it. Let me re-discuss with the team

15

For me, this topic is probably more important than anything else you guys are doing. Having all modules with changes that should not be committed is major pain for me:

  1. As a developer - I have to move them to changelist that should not be committed
  2. It causes conflicts when other developers commit the changes and I merge from them
  3. As a code reviewer I have to ask others to revert these changes if present in merge requests

All in all - this causes waste of time for great number of developers that could be better spent in real development activities.

2 Likes
16

With bigger teams this has become unmanageable

Can we move this to .idea/workspace.xml OR .idea/misc.xml

19

To give an update on this topic, we understand the pain it provides and have spent some time bootstrapping a solution to the problem. We will try to provide a fix in the upcoming release; you can keep an eye on the progress via this ticket that was mentioned earlier.

20

We just released SonarLint 10.4.2, which includes a workaround to this issue. We do not generate a UUID per module anymore as we now rely on our already existing sonarlint.xml in the .idea folder to store the necessary information (which does not rely on UUID anymore, but on tracking the module name changes).

Please have a try and see if the problem got resolved. Note that if you have resolved some anticipated issues (an issue existing locally only and not yet found on SonarQube/SonarCloud), they will be lost when switching to the new version.

1 Like