SonarQube version - Community Edition - Version 9.9.4
Resources:
OS - Windows
DB - Postgres
Java - 17
On a local install on a windows machine with the above resource, once a scan is triggered, subfolders for modules are being skipped for no obvious reason. Am I missing a flag from the below cmd call to set additional properties?
mvn sonar:sonar -Dsonar.projectKey=admin -Dsonar.host.url=http://localhost:9000 -Dsonar.login=sqp_********
Hi,
what’s your version of sonar maven plugin and how is the layout / structure of your sources ?
Additional details, see this thread
https://sonarsource.atlassian.net/browse/SCANMAVEN-190
Gilbert
Here’s my layout/structure:
my-multi-module-project/
├── pom.xml # Parent POM
├── module1/
│ └── pom.xml
├── module2/
│ └── pom.xml
└── module3/
└── pom.xml
My Sonar maven plugin version - 4.0.0.4121
And the layout of the module subfolders is maven standard, means
/module/src/main/java ?
You may run your build with loglevel DEBUG to get all details,
then attach the log - with sensitive parts redacted - as file to your answer
mvn -X clean verify sonar:sonar -Dsonar.projectKey=admin -Dsonar.host.url=http://localhost:9000 -Dsonar.login=sqp_********
Hi Gilbert.
Yes the layout of the module subfolders are standard as stated. There is however one more thing to consider before digging into the logs. Initially I did not have any xml plugins in my local install extensions/plugins folder. I eventually got a ‘sonar-xml-plugin’ in JAR from the maven repository with version number 2.10.0.4108 and placed it in the extensions/plugins folder as per instructions from the Sonar guide. Now I have to restart the application for the change to apply however this is where a new problem occurs with failed startup messages indicating plugins can’t be loaded.
“app[startup] Startup failed: Plugins can’t be loaded. See web logs for more information”
See attached screenshots
Hi Michael,
the days when you were able to update the sonar plugins one by one are long gone.
Nowadays if you need to update a sonar plugin - i.e. to support the latest version of java -
you’re forced to update your whole Sonarqube instance.
Sonarqube Community Edition 9.9.4, see
https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-9.9.4.87374.zip
ships with sonarqube-9.9.4.87374\lib\extensions\sonar-xml-plugin-2.7.0.3820.jar
so there’s already a sonar-xml installed.
Sonarqube Community Edition 10.6.0 latest, see
https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-10.6.0.92116.zip
ships with sonarqube-10.6.0.92116\lib\extensions\sonar-xml-plugin-2.10.0.4108.jar
means the version you’ve tried to install is compatible with Sonarqube 10.6.0
I’m nearly 100% sure the sonar-xml plugin is not responsible for your problem, you should provide the debug log of the maven build + the pom.xml to get further insights.
Of course the /extensions/plugins/sonar-xml-plugin-2.10.0.4108.jar has to be deleted.
Gilbert
