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

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

pmd:check – Apache Maven PMD Plugin

Full name:

org.apache.maven.plugins:maven-pmd-plugin:3.27.0:check

Description:

Fails the build if there were any PMD violations in the source code.

Attributes:

• Requires a Maven project to be executed.
• The goal is thread-safe and supports parallel builds.
• Since version: 2.0.
• Binds by default to the lifecycle phase: verify.
• Invokes the execution of the following plugin's goal prior to executing itself: pmd.

Deprecated.
since 3.15.0 Use the goal pmd:aggregate-check or pmd:aggregate-cpd-check instead.

Deprecated.
since 3.15.0 Use the goal pmd:aggregate-check or pmd:aggregate-cpd-check instead.

Whether to build an aggregated report at the root, or build individual reports.

• Type: boolean
• Since: 2.2
• Required: No
• User Property: aggregate
• Default: false

File that lists classes and rules to be excluded from failures. For PMD, this is a properties file. For CPD, this is a text file that contains comma-separated lists of classes that are allowed to duplicate.

• Type: java.lang.String
• Since: 3.0
• Required: No
• User Property: pmd.excludeFromFailureFile

Whether to fail the build if the validation check fails. The properties failurePriority and maxAllowedViolations control under which conditions exactly the build should be failed.

• Type: boolean
• Required: Yes
• User Property: pmd.failOnViolation
• Default: true

What priority level to fail the build on. PMD violations are assigned a priority from 1 (most severe) to 5 (least severe) according to the rule's priority. Violations at or less than this priority level are considered failures and will fail the build if failOnViolation=true and the count exceeds maxAllowedViolations. The other violations will be regarded as warnings and will be displayed in the build output if verbose=true. Setting a value of 5 will treat all violations as failures, which may cause the build to fail. Setting a value of 1 will treat all violations as warnings. Only values from 1 to 5 are valid.

• Type: int
• Required: Yes
• User Property: pmd.failurePriority
• Default: 5

The maximum number of failures allowed before execution fails. Used in conjunction with failOnViolation=true and utilizes failurePriority. This value has no meaning if failOnViolation=false. If the number of failures is greater than this number, the build will be failed. If the number of failures is less than or equal to this value, then the build will not be failed.

• Type: int
• Since: 3.10.0
• Required: No
• User Property: pmd.maxAllowedViolations
• Default: 0

Print details of errors that cause build failure

• Type: boolean
• Since: 3.0
• Required: No
• User Property: pmd.printFailingErrors
• Default: false

Skip the PMD checks. Most useful on the command line via "-Dpmd.skip=true".

• Type: boolean
• Required: No
• User Property: pmd.skip
• Default: false

The location of the XML report to check, as generated by the PMD report.

• Type: java.io.File
• Required: Yes
• User Property: project.build.directory

Print details of check failures to build output.

• Type: boolean
• Required: No
• User Property: pmd.verbose
• Default: false

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