No, this really means the header and footer of the report page, not the
table itself.
We have a PR in the pipe to make the table fully customizable:
https://github.com/jacoco/jacoco/pull/382
Regards,
-marc
On 2016-09-28 17:49, syashwan...@gmail.com wrote:
Thanks for your help. Apologies
Thanks for your help. Apologies for bringing up such questions.
One request from the change log I see in 0.7.7.
"New parameters title and footer for Maven reporting goals allow customization
of generated reports."
Does the above feature imply we can customise the report to check the covered
JaCoCo is agnostic to the way you run your tests.
If you can execute your tests without JaCoCo, then execution of tests with
JaCoCo shouldn't differ.
Make sure that you generate reports on a correct stage, i.e. if your tests
are execuetd as "integration tests" ( maven-failsafe-plugin or
Thanks for details.
I have gone through these documents but i didn't find any unit test files
are ran using junit in the ant offline instrumentation example.
Also when i ran the below mentioned build.xml (which is from offline
instrumentation) it's not working and i am getting the error
Hi,
Yes it is possible starting from version 0.7.7 , which introduced
"report-aggregate" Maven mojo -
see http://www.eclemma.org/jacoco/trunk/doc/report-aggregate-mojo.html
Build of JaCoCo itself utilizes this feature -
see
Hi,
Looking on innermost message of stack trace - "Can't add different class
with same name: org/jvnet/lafplugin/ComponentPluginManager", I'm pretty
sure that you need to exclude duplicates of class from report or put them
into different group. See "Why do I get an error when I try to analyze
Hi,
Thanks a lot for the quick reply. From the information you have provided I
could create a sample multi-module project and was successfully able to
replicate the same thing I was asking in the above request. But that was all
using unit tests only.
Majority of the test cases we use are
