I've opened "PMD Plugin reporting existing warnings as new" https://issues.jenkins-ci.org/browse/JENKINS-14509
- David On Thursday, July 19, 2012 4:58:45 PM UTC+3, Ulli Hafner wrote: > > Seems that the context hash code is not computed. Are the filenames > correct? Is this a maven or freestyle job? > > Can you please file an issue so we can discuss this problem in Jira? > > Ulli > > On 07/19/2012 01:35 PM, abune...@gmail.com wrote: > > Which file plug-in file created file do you need exactly? > jenkins\jobs\job-name\builds\2012-07-19_13-38-36\pmd-warnings.xml? > > Would it be enough for me to find the equivalent entries in the > pmd.xml/pmd-warnings.xml files? > > For example: > > pmd.xml: > <violation beginline="29" endline="29" begincolumn="31" endcolumn="84" > rule="LoggerIsNotStaticFinal" ruleset="Java Logging" > package="com.dbconfig.app" class="BackupDatabase" variable="logger" > externalInfoUrl= > "http://pmd.sourceforge.net/rules/java/logging-java.html#LoggerIsNotStaticFinal";<http://pmd.sourceforge.net/rules/java/logging-java.html#LoggerIsNotStaticFinal>priority="2"> > The Logger variable declaration does not contain the static and final > modifiers > </violation> > > pmd-warnings.xml: > <bug> > <message>The Logger variable declaration does not contain the static > and final modifiers.</message> > <priority>HIGH</priority> > <key>3660</key> > <lineRanges> > <range> > <start>29</start> > <end>29</end> > </range> > </lineRanges> > <primaryLineNumber>29</primaryLineNumber> > > <fileName>/home/jenkins/slave-root/workspace/job-name/db-config/src/main/java/com/dbconfig/app/BackupDatabase.java</fileName> > <moduleName reference="../../bug[20]/moduleName"/> > <packageName reference="../../bug[31]/packageName"/> > <category>Java Logging</category> > <type>LoggerIsNotStaticFinal</type> > <contextHashCode>3661</contextHashCode> > <origin>pmd</origin> > <pathName>db-config/src/main/java/com/dbconfig/app</pathName> > <primaryColumnStart>31</primaryColumnStart> > <primaryColumnEnd>84</primaryColumnEnd> > <tooltip></tooltip> > </bug> > > > - David > > On Thursday, July 19, 2012 12:31:15 PM UTC+3, Ulli Hafner wrote: > > Can you please file a bug report and attach the pmd warnings files > that are created by my plug-in (in the build folder) so I can compare these > two files...? > > Ulli > > On 07/19/2012 10:51 AM, abune...@gmail.com wrote: > > Yes, definitely the same PMD version. Before the PMD upgrade there > were no PMD warnings. > > > > The amount of warnings that are detected as new or existing seems > almost random. It usually shows all warnings as new, but it sometimes > detects some 10's or 100's as existing. > > > > - David > > > > On Thursday, July 19, 2012 11:29:16 AM UTC+3, Ulli Hafner wrote: > > > > Is the current and reference build using the same PMD version? > Maybe the > > IDs of the rules changed in PMD5... > > > > Ulli > > > > On 07/19/2012 09:59 AM, abune...@gmail.com wrote: > > > Hi, > > > > > > I'm using the PMD plugin to detect and monitor PMD warnings > that are > > > found in my builds. I recently upgraded to PMD 5.0 and added a > number > > > of new PMD rules to my report. > > > > > > My problem is that the PMD plugin seems to be almost completely > > > incapable of differentiating between new and previously found > PMD > > > warnings. > > > > > > For example, I got this from a recent build: > > > PMD: 1,306 warnings from one analysis. > > > > > > 1,304 new warnings > > > 1,305 fixed warnings > > > > > > Other types of warnings analyses (e.g. findbugs, checkstyle) > get it > > > right and are able to differentiate between new and old > warnings. > > > > > > Is this a known issue related to PMD 5? Any workarounds? > > > > > > Thanks, > > > David > > > > > > Jenkins 1.474 > > > Jenkins Violations Plugin 0.7.10 > > > PMD Plugin 3.29 > > > Static analysis utilities 1.43 > > > Static analysis collector plugin 1.29 > > > > >
