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

Reijo Tomperi edited comment on MPMD-163 at 2/19/13 6:10 AM:
-------------------------------------------------------------

I see this problem also. You can see the duplicates if you create a project 
with two files in the same package A.java and B.java. If there is a violation 
in B.java, then it is reported twice. If the violation is in A.java, it gets 
reported only once. If you have A, B and C. Then violations in C are reported 3 
times etc. Also files in other folders can affect this (but that gets more 
complicated to follow). I tested this with this file:

import java.util.ArrayList;
public class Foo
{
    public Foo(final ArrayList<String> foo)
    {
    }
}

Also note that I don't see this problem when using standalone PMD, so this 
seems to be issue in the PMD plugin itself. I'm using Apache Maven 2.2.1. 
                
      was (Author: dvice):
    I see this problem also. You can see the duplicates if you create a project 
with two files in the same package A.java and B.java. If there is a violation 
in B.java, then it is reported twice. If the violation is in A.java, it gets 
reported only once. If you have A, B and C. Then violations in C are reported 3 
times etc. Also files in other folders can affect this (but that gets more 
complicated to follow). I tested this with this file:

import java.util.ArrayList;
public class Foo
{
    public Foo(final ArrayList<String> foo)
    {
    }
}

Also note that I don't see this problem when using standalone PMD, so this 
seems to be issue in the PMD plugin itself. 
                  
> 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
>            Priority: Blocker
>
> 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: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to