Uploaded image for project: 'Maven PMD Plugin'
  1. Maven PMD Plugin
  2. MPMD-133

Parameters for pmd:check/cpd-check should be separate from pmd:pmd/cpd

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.5
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                sewe Andreas Sewe
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: