Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 84DDBFDFF for ; Mon, 1 Apr 2013 19:33:16 +0000 (UTC) Received: (qmail 196 invoked by uid 500); 1 Apr 2013 19:33:15 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 146 invoked by uid 500); 1 Apr 2013 19:33:15 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 138 invoked by uid 99); 1 Apr 2013 19:33:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Apr 2013 19:33:15 +0000 Date: Mon, 1 Apr 2013 19:33:15 +0000 (UTC) From: "Robert Muir (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (LUCENE-3973) Incorporate PMD / FindBugs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LUCENE-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-3973: -------------------------------- Labels: newdev (was: ) > Incorporate PMD / FindBugs > -------------------------- > > Key: LUCENE-3973 > URL: https://issues.apache.org/jira/browse/LUCENE-3973 > Project: Lucene - Core > Issue Type: Improvement > Components: general/build > Reporter: Chris Male > Labels: newdev > Attachments: core.html, LUCENE-3973.patch, LUCENE-3973.patch, LUCENE-3973.patch, LUCENE-3973.patch, LUCENE-3973.patch, 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 For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org