[MPMD-133] Parameters for pmd:check/cpd-check should be separate from pmd:pmd/cpd

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Auto Closed
• Affects Version/s: 2.5
• Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
• Assignee: Unassigned
• Reporter: Andreas Sewe
• Created: 18/Nov/11 05:29
• Updated: 16/Mar/18 22:40
• Resolved: 16/Mar/18 22:40

Description

Currently, the pmd:check and pmd:cpd-check goals do not have, e.g., their own minimumPriority parameter; they re-use the parameter values from pmd:pmd and pmd:cpd. This design makes it tricky to configure, e.g., a pmd:check execution that fails the build only on severe violations while at the same time having PMD/CPD reports which also report less severe violations.

The only (counter-intuitive) way I can think of is configuring the stricter minimumPriority in the pluginManagement and then overriding it with a laxer value in the reportPlugin's configuration. Configuring the {pmd:check}} execution directly, which is a much more intuitive way to achieve the same effect, is currently impossible.

Issue Links

• relates to: MPMD-190 Seperate CPD configuration from PMD i.e. exclude/include paths