模块“ M1：M1”已经是项目“ P1”的一部分

Question

We have 2 sonar projects (P1 & P2) running on 2 different/independent GIT repositories (G1 & G2) . Both the projects run on different branches (P1 runs on B1 & P2 runs on B2 ).

we have 2 plugins/modules named M1 & M2 in both GITs G1 and G2 on different branches.

1. In sonar project P1 we have analysis & coverage for 2 modules (M1 & M2) .

2. In sonar project P2 we have ignored these 2 modules (M1 & M2) both from analysis and coverage. ie, i have included them in "sonar.coverage.exclusions" and "sonar.exclusions" . Even then when we run sonar project P2 we are getting error

Error message :

Module "M1:M1" is already part of project "P1"

Module "M2:M2" is already part of project "P1"

I am curious why this error is displayed as they are from different GIT repositories and different branches of them.

Kindly suggest how can i resolve this issue. thank you.

Answer 1

It is not very intuitive that beside project names also the module names need to be unique in sonarqube. I think there might be a difference adding exclusions and disable the sonar report for that module. exclusions might still lead to some report.

So I would disable the sonar report for these to modules via the skip property:

<sonar.skip>true</sonar.skip>

in the pom files of the two modules you don't want to have reported again.

that should avoid having the sonar plugin trying to create such a module in sonar. In the worst case you may need to delete an older project in sonar that already contains that module where it does not belong. Then re-create the reports.