We have a case when several projects are configured in the sonar. Do all projects have different modules with the same name?

Question

We have a case when several projects are configured in the sonar. All projects have different modules with the same name.

At the same time, when and when we perform sonar for one of the projects, the execution ends with an error below.

[ERROR] Failed to complete the goal org.codehaus.mojo: sonar-maven-plugin: 2.6: sonar (default-cli) in project XXX: Module "XXXX" is already part of the project "YYYY" → [Help 1] org.apache .maven.lifecycle.LifecycleExecutionException: The target org.codehaus.mojo: sonar-maven-plugin: 2.6: sonar (default-cli) in project XXXX failed: The YYYY module is already part of the YYYY project,

It seems that since the module name is the same, Sonar completes the execution. Please note that we are using sonar version 3.5.5 and encounter this problem. Although we previously used the sonar version 4.1.1, and with this version the execution was successful (probably the sonar overlapped the previous report with the new one in case of a module name conflict).

Please suggest a possible solution for this? Thanks,

The full error log is available here.

https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/sonarqube/-L7cby77-28/6L6zPlb6AAAJ

Answer 1

I think you need to rename modules, for example if your project is abc. Please change your modules, for example abc_xxx etc., this may work for you.

Answer 2

Have you tried using the project name property?

In the pom.xml file:

<sonar.projectName>Some project name here</sonar.projectName>