[
https://jira.codehaus.org/browse/MPMD-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320512#comment-320512
]
Florent PAILLARD commented on MPMD-163:
---------------------------------------
Great! I haven't seen it, my local Maven proxy was not up-to-date.
Works perfectly with 3.1-SNAPSHOT.
Thanks Oliver
> PMD issues are reported multiple times
> --------------------------------------
>
> Key: MPMD-163
> URL: https://jira.codehaus.org/browse/MPMD-163
> Project: Maven 2.x PMD Plugin
> Issue Type: Bug
> Components: PMD
> Affects Versions: 3.0
> Environment: Apache Maven 3.0.4
> Sun jdk1.6.0_04 on Debian Lenny
> Oracle jdk 1.7.0_13 on Mac OS X (10.8.2)
> Reporter: Mirko Friedenhagen
> Assignee: Olivier Lamy
> Priority: Blocker
> Fix For: 3.1
>
> Attachments: MPMD-163-against-tag-3.0.patch, my-app.zip
>
>
> After updating maven-pmd-plugin from 2.7.1 to 3.0, in some of our projects
> the number of pmd violations exploded. Some are valid (new rules), however I
> have a project where the same violation will show up more than 70 times!
> See below for an example of this dramatic outcome:
> {code}
> [mifr@host SomeService]$ grep '^<violation' target/pmd.xml | wc
> 3682 44655 1239557
> [mifr@host SomeService]$ grep '^<violation' target/pmd.xml | sort | uniq | wc
> 92 1120 30832
> {code}
> The number of source files in this project in total is 96, so a wild guess
> would be, that the plugin readds already existing violations (the first
> (unique) violation occurs once, the second 4 times and so on). I will try t
> take a look at the source code or to get a working testcase.
--
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
