Maven Multimodule error (Please provide compiled classes of your project with sonar.java.binaries property)

[cipher]

I am using sonarqube version 6.7

I am running my multi module maven project, each module has pom.xml and targets in it,
Now all modules are triggered via a superpom.xml when I am just calling the other modules, so when I trigger superpom.xml, it creates the targets in each respective module.
I am integrated Jenkins with sonarqube and when I am trying build the code it throws error as,
INFO: Source paths: src
INFO: Source encoding: UTF-8, default locale: en_IN
INFO: Language is forced to java
INFO: Index files
INFO: 11 files indexed
INFO: Quality profile for java: Sonar way
INFO: Sensor JavaSquidSensor [java]
INFO: Configured Java source version (sonar.java.source): none
INFO: JavaClasspath initialization
INFO: ------------------------------------------------------------------------
INFO: EXECUTION FAILURE
INFO: ------------------------------------------------------------------------
INFO: Total time: 4.187s
INFO: Final Memory: 30M/2350M
INFO: ------------------------------------------------------------------------
ERROR: Error during SonarQube Scanner execution
ERROR: Please provide compiled classes of your project with sonar.java.binaries property
ERROR:
ERROR: Re-run SonarQube Scanner using the -X switch to enable full debug logging.
ERROR: SonarQube scanner exited with non-zero code: 1
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Finished: FAILURE

Please suggest how can I scan the multi module scenario in this case.

[ganncamp (G Ann Campbell)]

Hi,

Are you actually compiling before you try to analyze?

 
Ann

[cipher]

Yes, I build parent pox.xml in which I call every module/subproject pom.xml and it compiles the project and builds the libs and binaries into respective subprojects and not in the parent module.

[Julien_HENRY]

Hi @cipher

It is hard to help you without more details. I would need the full logs of the build + analysis (mvn verify sonar:sonar) or even better, a small project that reproduce the issue.