lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Male (Updated) (JIRA)" <>
Subject [jira] [Updated] (LUCENE-3973) Incorporate PMD / FindBugs
Date Sat, 14 Apr 2012 04:37:13 GMT


Chris Male updated LUCENE-3973:

    Attachment: LUCENE-3973.patch

Simple POC patch which adds a pmd target to lucene/common-build.xml.  It currently uses ivy:cachepath
(but I think I prefer the way Hoss suggests).

I will attach some example results from analyzing lucene/solr core.

In our build system, is it possible to run a target for every module? I don't really want
to latch this onto {{compile}} like clover.

Still much to do but just showing where things are going.
> Incorporate PMD / FindBugs
> --------------------------
>                 Key: LUCENE-3973
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: general/build
>            Reporter: Chris Male
>         Attachments: LUCENE-3973.patch, core.html, solr-core.html
> This has been touched on a few times over the years.  Having static analysis as part
of our build seems like a big win.  For example, we could use PMD to look at {{System.out.println}}
statements like discussed in LUCENE-3877 and we could possibly incorporate the nocommit /
@author checks as well.
> There are a few things to work out as part of this:
> - Should we use both PMD and FindBugs or just one of them? They look at code from different
perspectives (bytecode vs source code) and target different issues.  At the moment I'm in
favour of trying both but that might be too heavy handed for our needs.
> - What checks should we use? There's no point having the analysis if it's going to raise
too many false-positives or problems we don't deem problematic.  
> - How should the analysis be integrated in our build? Need to work out when the analysis
should run, how it should be incorporated in Ant and/or Maven, what impact errors should have.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message