PMD is a static code analyzer (like FindBugs). It seeks potential problems like:
Possible bugs - empty try/catch/finally/switch statements Dead code - unused local variables, parameters and private methods Suboptimal code - wasteful String/StringBuffer usage Overcomplicated expressions - unnecessary if statements, for loops that could be while loops Duplicate code - copied/pasted code means copied/pasted bugs I like running code analyzers to find subtle issues. We should be concerned because people, like me, run these analyzers on code they bring inside organizations. And we want the code to be as clean as possible. On Sun, Mar 4, 2012 at 9:41 PM, John Vines <[email protected]> wrote: > I am not familiar with this pmd module. A cursory glance over things makes > it seem like it's for documenting our procedures, but why should we be > concerned with a module we don't use being broken? > > John > > On Sun, Mar 4, 2012 at 9:22 PM, David Medinets > <[email protected]>wrote: > >> I am seeing this warning when running 'mvn pmd:pmd': >> >> The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, >> no dependency information available >> >> I was able to eliminate this message using a project on github: >> >> git clone git:// >> github.com/mfriedenhagen/dummy-lifecycle-mapping-plugin.git >> cd dummy-lifecycle-mapping-plugin >> mvn install >> >> This is a minor issue, but it might be nice to add the fix to an FAQ. >>
