[jira] (MPMD-166) Plugin fails when switching from 2.7.1 to 3.0.1

["Andreas Dangel (JIRA)" <ji...@codehaus.org>]

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

Andreas Dangel commented on MPMD-166:
-------------------------------------

maven-pmd-plugin 3.0.1 uses internally PMD 5 which has some incompatible changes, e.g. where the default rulesets are located.

In order to fix this, you'll need to change the ruleset configuration to the following:

{noformat}
<rulesets>
  <ruleset>/rulesets/java/basic.xml</ruleset>
  <ruleset>/rulesets/java/unusedcode.xml</ruleset>
  <ruleset>/rulesets/java/junit.xml</ruleset>
  <ruleset>/rulesets/java/braces.xml</ruleset>
  <ruleset>/rulesets/java/codesize.xml</ruleset>
  <ruleset>/rulesets/java/logging-java.xml</ruleset>
</rulesets>
{noformat}

You basically need to add *java* to the ruleset path.

                
> Plugin fails when switching from 2.7.1 to 3.0.1
> -----------------------------------------------
>
>                 Key: MPMD-166
>                 URL: https://jira.codehaus.org/browse/MPMD-166
>             Project: Maven 2.x PMD Plugin
>          Issue Type: Bug
>          Components: PMD
>    Affects Versions: 3.0
>            Reporter: Brett VanderVeen
>            Priority: Minor
>         Attachments: console.log, pom.xml
>
>
> When running {{mvn clean deploy findbugs:findbugs}} on our modular Maven project, we receive an *BUILD ERROR*: {{[PMD] No report found for mojo pmd}}
> I have attached the console log and the pom file where the plugin is included (parent pom for the project).
> All that is changed is the version, from {{2.7.1}} to {{3.0.1}}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira