I remember some discussions on the mailing list I can't find at the moment but I try to outline the differences form point of view:
+) Checkstyle was target for source code readability such as coding style, length of lines, complaints about missing JAVADOC (very useful but my code misses a lot of JAVADOC) +) PMD is a static source code analyzer which overlaps with Checkstyle regarding the source code readability +) PMD provides a couple of essential features such as unused instance variable, unused local variables and unused formal parameter, unused private methods and duplicate imports and some hints about design patterns. +) For PMD there are some new rules discussed (well, call it my wish list) such as detecting string literals (I saw production code infected with hard-coded SQL statements), System.exit() (kills an application server neatly), usage for System.out and System.err (a brilliant idea to dump a stack trace on System.err and then call System.exit()), the forgotten System.gc() call I found recently within a library killing the performance ... There were discussion about merging the tools but personally I quite happy with both reports. Sigi Send reply to: "Turbine Maven Users List" <[EMAIL PROTECTED]> Date sent: Tue, 27 Aug 2002 19:45:32 -0500 From: Barry Kaplan <[EMAIL PROTECTED]> To: Turbine Maven Users List <turbine- [EMAIL PROTECTED]> Subject: Re: PMD Maven-plugin available .... > > > > > >PMD is a Java Source Code Analyzer complementing > >the existing CheckStyle plugin. > > > Looks quite nice. Could you describe bit how it compliments CheckStyle? > Kinda looks like a replacement. > > -bk > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
