-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
There are some benefits on using xml reports instead of exec-files
- no dependency of jacoco.jar needed, so reports will be always actual no matter what jacoco version created them (currently reports created by newer version of jacoco do not take any effect because jacoco-plugin's dependency is older);
- xml report contains all the information needed not to lose in the functionality of the plugin; report contains class, package, method coverage and their name - everything that is necessary for the plugin to work;
- in case of xml report - this report can be generated by the build tool or even by the jacoco's cli giving user more flexibility in configuring his build pipeline
- xml reports from any other coverage tools (scoverage, cobertura, etc.) can be easily converted into jacoco's xml format and get all the benefits of this plugin (reporting, dashboard views, etc.)
[JENKINS-56210] Analyze JaCoCo's xml report instead of exec-files
Nikolay Metchev
added a comment - this will help with our gradle build where we are using the kover plugin and the intellij engine. That engine doesn't produce an exec file but it does produce an xml file.
Nikolay Metchev
added a comment - this will help with our gradle build where we are using the kover plugin and the intellij engine. That engine doesn't produce an exec file but it does produce an xml file. 
There has been some discussion on this before, but unfortunately nobody took the task of actually working on it so it will likely not happen until someone invest the necessary time to contribute and maintain such a feature (ideally as non-default option first to not break all existing installations).