This is the only reliably way that I found to avoid checking generated
code and resources. See also e.g.
http://stackoverflow.com/questions/
2362652/excluding-classes-in-maven-checkstyle-plugin-reports
and my comment on that page.
Change-Id: I8b2ec5ee6d46dc108e781031996a1022b8c5330a
Signed-off-by: Michael Vorburger <vorburger@redhat.com>
--- /dev/null
+<?xml version="1.0"?>
+<!DOCTYPE suppressions PUBLIC
+ "-//Puppy Crawl//DTD Suppressions 1.1//EN"
+ "http://www.puppycrawl.com/dtds/suppressions_1_1.dtd">
+<!--
+ Copyright (c) 2016 Red Hat, Inc. and others. All rights reserved.
+
+ This program and the accompanying materials are made available under the
+ terms of the Eclipse Public License v1.0 which accompanies this distribution,
+ and is available at http://www.eclipse.org/legal/epl-v10.html
+-->
+<suppressions>
+
+ <suppress files="[/\\]target[/\\]" checks=".*"/>
+
+</suppressions>
<property name="format" value="(\r\n|\r)"/>
<property name="message" value="Line has Windows line delimiter."/>
</module>
+ <module name="SuppressionFilter">
+ <property name="file" value="${checkstyle.suppressions.file}" />
+ </module>
<module name="SuppressWarningsFilter"/>
<module name="TreeWalker">
<module name="RegexpSinglelineJava">
</dependencies>
<configuration>
<configLocation>odl_checks.xml</configLocation>
+ <suppressionsLocation>checkstyle-suppressions.xml</suppressionsLocation>
<!-- <sourceDirectory> is needed so that checkstyle ignores the
generated sources directory -->
<sourceDirectory>${project.build.sourceDirectory}</sourceDirectory>