It depends on whether you use a project like Freestyle or an Evil Maven project project .
If you are using freestyle, you just need to set the template for the results of checkstyle.xml to exclude aggregator or exclude subprojects.
If you use an evil brother, you may need to configure the per-module configuration to disable reports for child modules.
The problem is that the aggregator module copies warnings from child projects to create an aggregated report.
You can also disable aggregation when the job is running on Jenkins.
This is basically the struggle between auto-impulse βmagicβ from an evil type of project and how the maven-checkstyle-plugin module implements aggregate reporting.
Stephen Connolly Nov 17 '12 at 20:52 2012-11-17 20:52
source share