I'm currently trying to improve the visualization of JaCoCo reports in Jenkins (https://github.com/jenkinsci/code-coverage-api-plugin/). The plugin reads a JaCoCo XML report and shows the details in Jenkins. While parsing the JaCoCo XML reports I noticed that packages (and so classes) are qualified only by the actual package path that starts right after the *source code path*. I.e., `package="/io/jenkins/"` and not `package="src/main/java/io/jenkins/"` or `package="/absolute/path/to/io/jenkins/"`. Is there a way to include the source code path in the XML file as well (or use the absolute path)? Otherwise I need to guess where the actual source code is stored (or I need to duplicate the JaCoCo option of specifying a source code path manually).
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 jacoco+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/88cfbbd8-72cd-4b02-868f-8b4e974ec003n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/97A31987-51E5-43BB-8849-8ADF1D2D6CC5%40mountainminds.com.
the tools you’re mentioning work on source code and need source code as an import anyways.
These new source attributes would have to be configured by the user anyways. We do this already for the HTML report but basically use lookup paths to find specific source files.
Your example with packages will probably not work as due to split-packages (think of main/test) there is not a single location for a package.
To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/33810F30-711A-4CEC-B21B-C100A66CD896%40mountainminds.com.