To best of our knowledge import of aggregate XML report into SonarQube works fine - https://github.com/jacoco/jacoco/commit/6babdb5233217b0812a85f6b1673aabe7f0fd47e
And in any case SonarQube integration is not developed by us and problems with third-party integrations should be discussed with their corresponding vendors. Here is SonarQube users forum that already contains guide and many other helpful threads about this subject - https://community.sonarsource.com/t/coverage-test-data-importing-jacoco-coverage-report-in-xml-format/12151 P.S. in absence of complete example demonstrating your difficulty, chances that someone will be able to blindly guess what is wrong in your configuration are very low. On Monday, August 12, 2019 at 11:11:36 AM UTC+2, [email protected] wrote: > > org.sonarsource.scanner.maven version: 3.6.0.1398 > jacoco.version: 0.8.4 > > > > Am Montag, 12. August 2019 11:05:41 UTC+2 schrieb [email protected]: >> >> We switched to a newer version of jacoco in order to report xml files for >> sonarqube. >> >> The Problem is that by creating a perfect report-aggregate xml sonarqube >> does not accept it. >> With normal reports in xml, this has not been a problem at all. >> >> Is this a known issue or did we setup something wrong? >> >> Could a problem be that we refer the xmlpath to the project.build ? >> >> There has to be some change that is necessary for report aggregate in >> comparisson >> to the normal report but i can not solve it on my own. >> >> Instrumentation is used as well as a specific module in a multi module >> project to create the report aggregate. >> All modules are dependencies in the aggregate module. >> > -- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/e0f175d5-22e0-4d72-b9ff-b44e2e41208f%40googlegroups.com.
