A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://maven.apache.org/plugins/maven-checkstyle-plugin/check-mojo.html below:

Apache Maven Checkstyle Plugin – checkstyle:check

Performs Checkstyle analysis and outputs violations or a count of violations to the console, potentially failing the build. It can also be configured to re-use an earlier analysis.

Parameter Details <cacheFile>

Specifies the cache file used to speed up Checkstyle on successive runs.

<checkstyleRules>

By using this property, you can specify the whole Checkstyle rules inline directly inside this pom.

<plugin>
  ...
  <configuration>
    <checkstyleRules>
      <module name="Checker">
        <module name="FileTabCharacter">
          <property name="eachLine" value="true" />
        </module>
        <module name="TreeWalker">
          <module name="EmptyBlock"/>
        </module>
      </module>
    </checkstyleRules>
  </configuration>
  ...
<checkstyleRulesHeader>

The header to use for the inline configuration. Only used when you specify checkstyleRules.

<configLocation>

Specifies the location of the XML configuration to use.

Potential values are a filesystem path, a URL, or a classpath resource. This parameter expects that the contents of the location conform to the xml format (Checkstyle Checker module) configuration of rulesets.

This parameter is resolved as resource, URL, then file. If successfully resolved, the contents of the configuration is copied into the ${project.build.directory}/checkstyle-configuration.xml file before being passed to Checkstyle as a configuration.

There are 2 predefined rulesets.

<consoleOutput>

Output errors to console.

<excludeGeneratedSources>

Specifies whether generated source files should be excluded from Checkstyle.

<excludes>

Specifies the names filter of the source files to be excluded for Checkstyle.

<failOnViolation>

Fail the build on a violation. The goal checks for the violations after logging them (if

logViolationsToConsole

is

true

). Compare this to

failsOnError

which fails the build immediately before examining the output log.

<failsOnError> <headerLocation>

Specifies the location of the License file (a.k.a. the header file) that can be used by Checkstyle to verify that source code has the correct license header.

You need to use ${checkstyle.header.file} in your Checkstyle xml configuration to reference the name of this header file.

For instance:

<module name="RegexpHeader">
  <property name="headerFile" value="${checkstyle.header.file}"/>
</module>
<includeResources>

Whether to apply Checkstyle to resource directories.

<includeTestResources>

Whether to apply Checkstyle to test resource directories.

<includeTestSourceDirectory>

Include or not the test source directory to be used for Checkstyle.

<includes>

Specifies the names filter of the source files to be used for Checkstyle.

<inputEncoding>

The file encoding to use when reading the source files. If the property project.build.sourceEncoding is not set, the platform default encoding is used. Note: This parameter always overrides the property charset from Checkstyle's TreeWalker module.

<logViolationCountToConsole>

Output the detected violation count to the console.

<logViolationsToConsole>

Output the detected violations to the console.

<maxAllowedViolations>

The maximum number of allowed violations. The execution fails only if the number of violations is above this limit.

<omitIgnoredModules>

Specifies whether modules with a configured severity of ignore should be omitted during Checkstyle invocation.

<outputFile>

Specifies the path and filename to save the Checkstyle output. The format of the output file is determined by the outputFileFormat parameter.

<outputFileFormat>

Specifies the format of the output to be used when writing to the output file. Valid values are "plain", "sarif" and "xml".

<propertiesLocation>

Specifies the location of the properties file.

This parameter is resolved as URL, File then resource. If successfully resolved, the contents of the properties location is copied into the ${project.build.directory}/checkstyle-checker.properties file before being passed to Checkstyle for loading.

The contents of the propertiesLocation will be made available to Checkstyle for specifying values for parameters within the xml configuration (specified in the configLocation parameter).

<propertyExpansion>

Allows for specifying raw property expansion information.

<resourceExcludes>

Specifies the names filter of the files to be excluded for Checkstyle when checking resources.

<resourceIncludes>

Specifies the names filter of the files to be used for Checkstyle when checking resources.

<rulesFiles>

Dump file for inlined Checkstyle rules.

<skip>

Skip entire check.

<skipExec>

Skip Checkstyle execution will only scan the outputFile.

<sourceDirectories>

Specifies the location of the source directories to be used for Checkstyle. Default value is ${project.compileSourceRoots}.

<sourceDirectory> Deprecated.

instead use

sourceDirectories

. For version 3.0.0, this parameter is only defined to break the build if you use it!

Specifies the location of the source directory to be used for Checkstyle.

<suppressionsFileExpression>

The key to be used in the properties for the suppressions file.

<suppressionsLocation>

Specifies the location of the suppressions XML file to use.

This parameter is resolved as resource, URL, then file. If successfully resolved, the contents of the suppressions XML is copied into the ${project.build.directory}/checkstyle-suppressions.xml file before being passed to Checkstyle for loading.

See suppressionsFileExpression for the property that will be made available to your Checkstyle configuration.

<testSourceDirectories>

Specifies the location of the test source directories to be used for Checkstyle. Default value is ${project.testCompileSourceRoots}.

<testSourceDirectory> Deprecated.

instead use

testSourceDirectories

. For version 3.0.0, this parameter is only defined to break the build if you use it!

Specifies the location of the test source directory to be used for Checkstyle.

<useFile>

If null, the Checkstyle plugin will display violations on stdout. Otherwise, a text file will be created with the violations.

<violationIgnore>

Violations to ignore. This is a comma-separated list, each value being either a rule name, a rule category or a java package name of rule class.

<violationSeverity>

The lowest severity level that is considered a violation. Valid values are "error", "warning" and "info".

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4