A RetroSearch Logo

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

Search Query:

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

pmd:aggregate-cpd-check – Apache Maven PMD Plugin

pmd:aggregate-cpd-check

Full name:

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

Description:

Fail the build in an aggregator project if there were any CPD violations in the source code.

Attributes:

Required Parameters Name Type Since Description <failOnViolation> boolean 3.0 Whether to fail the build if the validation check fails.
Default: true
User Property: cpd.failOnViolation <targetDirectory> File - The location of the XML report to check, as generated by the PMD report.
User Property: project.build.directory Optional Parameters Name Type Since Description <aggregate> boolean 2.2

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.
Default: false
User Property: aggregate <excludeFromFailureFile> String 3.0 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.
User Property: pmd.excludeFromFailureFile <maxAllowedViolations> int 3.10.0 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.
Default: 0
User Property: pmd.maxAllowedViolations <printFailingErrors> boolean 3.0 Print details of errors that cause build failure
Default: false
User Property: pmd.printFailingErrors <skip> boolean - Skip the CPD violation checks. Most useful on the command line via "-Dcpd.skip=true".
Default: false
User Property: cpd.skip <verbose> boolean - Print details of check failures to build output.
Default: false
User Property: pmd.verbose Parameter Details <aggregate>

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.

<excludeFromFailureFile>

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.

<failOnViolation>

Whether to fail the build if the validation check fails.

<maxAllowedViolations>

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.

<printFailingErrors>

Print details of errors that cause build failure

<skip>

Skip the CPD violation checks. Most useful on the command line via "-Dcpd.skip=true".

<targetDirectory>

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

<verbose>

Print details of check failures to build output.


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