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 > >
