maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Sewe (JIRA)" <j...@codehaus.org>
Subject [jira] (MPMD-133) Parameters for pmd:check/cpd-check should be separate from pmd:pmd/cpd
Date Thu, 12 Jan 2012 08:57:03 GMT

    [ https://jira.codehaus.org/browse/MPMD-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288095#comment-288095
] 

Andreas Sewe commented on MPMD-133:
-----------------------------------

OK, figured out that that's what {{pmd:check}}'s {{failurePriority}} parameter is for. (Using
it you can configure {{pmd:check}} to fail on only a subset of checks {{pmd:pmd}} performs.)

Originally, I was trying to get {{pmd:check}} to run with its own, less strict {{minimumPriority}}
value. This was ugly to configure, as the {{pmd:check}}'s execution cannot be told another
value for {{minimumPriority}}.

Anyway, I think this use case should be documented on the plugin's site: http://maven.apache.org/plugins/maven-pmd-plugin/examples/violationChecking.html.
                
> 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

        

Mime
View raw message