Hi Nick,
if those extra methods generated would be marked as synthetic (which
would be a good practice), JaCoCo will not report them. Maybe you report
this issue to OpenJPA.
With JaCoCo we do not yet have filtering options on method level. Future
versions of JaCoCO might have this.
Cheers,
-marc
On 22.08.14 18:12, [email protected] wrote:
Hi,
Sorry if this is an FAQ, but I've spent quiet some time with Google to no avail.
We are using Apache OpenJPA (2.2.2) for Java Persistence of our Entity objects,
and have recently switched from Cobertura to JaCoCo (due to JVM 7 issues).
Suddenly, our coverage has dropped from 80% to 35%, which causes our build to
fail, due to our JaCoCo coverage check in the verify stage.
When I run the maven site lifecycle, I see a bunch of methods with minimal
coverage (especially branch coverage) on the entity classes which are enhanced
by the OpenJPA maven plugin (for example, pcReplaceField, pcCopyField,
pcIsDetached, static {}, etc). Of course, these report links don't point to any
lines of code in the report.
Is there any way that JaCoCo could ignore these generated methods (like
Cobertura seems to)?
Thanks,
Nick.
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
