Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: general/build
    • Labels:
    • Lucene Fields:
      New

      Description

      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.
      1. LUCENE-3973.patch
        0.9 kB
        Chris Male
      2. core.html
        472 kB
        Chris Male
      3. solr-core.html
        382 kB
        Chris Male
      4. LUCENE-3973.patch
        2 kB
        Chris Male
      5. LUCENE-3973.patch
        2 kB
        Chris Male
      6. LUCENE-3973.patch
        3 kB
        Robert Muir
      7. LUCENE-3973.patch
        5 kB
        Chris Male

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              Chris Male
            • Votes:
              2 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Development