As Andrea said, the
sonar.testExecutionReportPaths is simply ignored when specified in the pom of a module.
The only way to trigger the execution of the Generic Test Execution Sensor is to specify the property in the root pom. However, although the sensor executes, it will complain about not being able to find the source files referenced in the reports. Reports are generated by child modules and often reference source files relative to their own base - such relative reference cannot be resolved from the root pom - hence the reason why the Sensor complains (executed from the root).
Although there is a way to trigger the execution of the Sensor - this is not a viable workaround since it will ultimately refuse to consider the content of the read reports
The solution is even more confusing that we can specify properties for other sensors in child poms without any problem. Please, have a look at this issue…
BTW: I confirm the issue is still there with SonarQube 8.2.
@reitzmichnicht Did you find any viable workaround for this multi-module setup ?
@ganncamp What’s the status about this issue? Any chance you’ll be looking at it in the near future?