Hi Matthew,
this typically happens when a class has invalid stackmap frames. Even if
the JVM has a fall-back to the old verififier in such situations, JaCoCo
accepts valid class files only. This is typically caused by other tools
or libraries modifying the Java bytecode (e.g. some persistence
implementations).
I could take a closer look, if you provide the class file
"com/xxx/xx/xx/xx/xxx" as seen by the JaCoCo agent. For this please
specify the 'classdumpdir' option to the JaCoCo agent (see
http://www.eclemma.org/jacoco/trunk/doc/agent.html).
Alternatively you might simply exclude the class in question.
Best regards,
-marc