-
New Feature
-
Resolution: Unresolved
-
Major
-
None
We need an option to exclude complete Maven modules from the JaCoCo report.
I've tried it with an exclusion pattern like **/module-to-be-excluded/**, but this doesn't work. It seems that the JaCoCo plugin copies the classes from all modules into a new directory, so the module folder names are lost and cannot be used for filtering any more.
Filtering on package/class level would be very cumbersome because other modules in the build typically use similar package names.
Thanks a lot for your assistance!
Best Regards,
Jochen Ehret.
[JENKINS-21658] Provide option to exclude complete Maven modules from JaCoCo report
Jochen Ehret
created issue -
Jochen Ehret
made changes -
| Description |
Original:
We need an option to exclude complete Maven modules from the JaCoCo report. I've tried it with an exclusion pattern like "**/module-to-be-excluded/**", but this doesn't work. It seems that the JaCoCo plugin copies the classes from all modules into a new directory, so the module folder names are lost and cannot be used for filtering any more. Filtering on package/class level would be very cumbersome because other modules in the build typically use similar package names. Thanks a lot for your assistance! Best Regards, Jochen Ehret. |
New:
We need an option to exclude complete Maven modules from the JaCoCo report. I've tried it with an exclusion pattern like \*\*/module-to-be-excluded/\*\*, but this doesn't work. It seems that the JaCoCo plugin copies the classes from all modules into a new directory, so the module folder names are lost and cannot be used for filtering any more. Filtering on package/class level would be very cumbersome because other modules in the build typically use similar package names. Thanks a lot for your assistance! Best Regards, Jochen Ehret. |
| Workflow | Original: JNJira [ 153657 ] | New: JNJira + In-Review [ 178563 ] |
