Mvn org.sonarsource.scanner.maven:sonar-maven-plugin change the target folder stucture

SonarQube Cloud
, ,
1

hi All
Our current github-action cicd pipeline is currently using mvn org.sonarsource.scanner.maven:sonar-maven-plugin:sonar to scan our project. After running sonar scan, I found that the target folder structure had changed.
This is the folder structure that existed before running the sonarscan:

image
image1591×173 32.5 KB

After running sonarscan, the classes folder as well as jar files and other folders that were supposed to be in the target folder were moved outside, and target folder was removed.
image
image1733×160 32.4 KB

could you please take a look at this issue ? thank you

Best
F.J

2

Hey there.

I’m not able to reproduce this – are you able to reproduce this locally outside of your Github action?

3

@Colin Hi, thank you for your quick response, i am not able to reproduce it in my local since it is via cicd pipeline. did i miss something?

4

I’m asking if you can try and reproduce it locally with this specific project, outside the context of your CI/CD pipeline.

5

@Colin
Yeah, i tried, same result, after i ran mvn sonarscan, it changed the folder structure.

6

And this only happens when you run mvn sonar:sonar, and not when you run mvn package or mvn verify (or whatever you normally do before Sonar analysis)?

I can’t reproduce this. It might help if you upload a sample project you can reproduce this issue on.

7

Yes, it only happens when after i run mvn sonar:sonar , the targer folder got changed then. how can i upload a sample project in here ? thank you

Best
FJ

8

Zipping it up and placing it here, or a public GitHub repo.