We are currently working on maven multi-module project, we have cross module tests so we have created a new module for aggregating the reports as stated in (https://github.com/jacoco/jacoco/wiki/MavenMultiModule).
The report aggregate goal works fine and generates only csv,xml and index.html files but does not generate an aggregated jacoco.exec file.
we need exec file to push it to sonarqube for analysis.
Please suggest a way where we can create aggregated exec file.
Thank you
Please suggest a way where we can create aggregated exec file.
we need exec file to push it to sonarqube for analysis.
Thanks for the reply.
Wanted to know if 'aggregate' and 'merge' perform the same task.
Because of cross module test cases the jacoco results generated in the child modules doesn't show the coverage of other modules.
I was able to get the cross module code coverage only on using 'aggregate' task(which did not generate jacoco.exec)
So basically as per my understanding merge task will just merge all the jacoco.exec from modules into one, but these jacoco.exec doesn't have the cross module code coverage.
Please correct me if I'm wrong
Thank you !!
So basically as per my understanding merge task will just merge all the jacoco.exec from modules into one, but these jacoco.exec doesn't have the cross module code coverage.
Please correct me if I'm wrong
On Thursday, December 7, 2017 at 6:57:24 PM UTC+5:30, Evgeny Mandrikov wrote:
On Thursday, December 7, 2017 at 12:53:04 PM UTC+1, prathi...@gmail.com wrote:So basically as per my understanding merge task will just merge all the jacoco.exec from modules into one, but these jacoco.exec doesn't have the cross module code coverage.
Please correct me if I'm wrong
You're wrong - exec file contains information about classes no matter from which module they come."report-aggregate" doesn't affect exec files in any way and uses exactly the same ones.If I am right, jacoco.exec will have the coverage information about the unit module and the depending module.
But I am not able to see the depending module coverage in Sonar. What could have I done wrong ? My sonar version is 5.6.7