> If future versions of JaCoCo may come with their own annotation (like
@ExcludeFromCodeCoverage) would a dependency on this JaCoCo annotations
work better for you?
A bit better, yes.
Honestly, the best option for me would be to have some "excludes" patterns
in build plugins. I saw this
Hi,
actually option 2 is the only one that works with the current release:
Annotate with one of the existing annotations @lombok.Generated or
@groovy.transform.Generated. If you define the annotations yourself make
sure the retention is CLASS.
If future versions of JaCoCo may come with their