SonarQube scan failing with "is already part of project XXX error is already part of project" -


recently upgraded sonarqube 4.0 4.3.3. post upgrade when try run maven build getting error:

failed execute goal org.codehaus.mojo:sonar-maven-plugin:2.4:sonar (default-cli) on project xxx on project yyy module "abc.def.xyz" part of project of other project.

the issue scan on multiple branches have modules same name.
there way turn off validation?

assume have multiple modules maven project below structure:

com.company:project     com.company:project-module1     com.company:project-module2 

in java source code, "com.company:project" renamed "com.company:myproject", new java source strucutre becomes:

com.company:myproject     com.company:project-module1     com.company:project-module2 

when build new source , push analysis data sonar, prompt:

[error] failed execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.2:sonar (default-cli) on project myproject: module "com.company:project-module1" part of project "com.company:project" -> [help 1]

this error because "com.company:project-module1" executed , registered sonar before , belongs "com.company:project" project whihc no longer exist in source code anymore.

solution: in sonar project configuration --> update key, change project "com.company:project" key "com.company:project" "com.company:myproject", rerun maven build , push sonar, issue solve.


Comments

Popular posts from this blog

python - mat is not a numerical tuple : openCV error -

c# - MSAA finds controls UI Automation doesn't -

wordpress - .htaccess: RewriteRule: bad flag delimiters -