[
https://jira.codehaus.org/browse/MPMD-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287442#comment-287442
]
Dennis Lundberg commented on MPMD-133:
--------------------------------------
Can you show us the configuration you have tried to use?
> Parameters for pmd:check/cpd-check should be separate from pmd:pmd/cpd
> ----------------------------------------------------------------------
>
> Key: MPMD-133
> URL: https://jira.codehaus.org/browse/MPMD-133
> Project: Maven 2.x PMD Plugin
> Issue Type: Improvement
> Affects Versions: 2.5
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Reporter: Andreas Sewe
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
