Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of edlinuxguru@gmail.com
 designates 209.85.213.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50169AE3.9050604@filez.com>
References: <500C0FD5.7020406@filez.com>
	<CALdd-zgLOvGF1gK2ooABhpEiksSd0upM7ttgLMF11Xu42D+5YA@mail.gmail.com>
	<500CFF9E.5060306@filez.com>
	<056051B0-156B-4EA9-8694-E408ECD01D6F@yahoo.com>
	<500DCC91.4060100@filez.com>
	<50169AE3.9050604@filez.com>
Date: Mon, 30 Jul 2012 10:47:51 -0400
Message-ID: 
 <CAENxBwzkwvFta44jppXxqk-u0C6mZH8sZaCq2OMCkYrzgUVRNg@mail.gmail.com>
Subject: Re: findbugs
From: Edward Capriolo <edlinuxguru@gmail.com>
To: dev@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I am sure no one would have an issue with an optional findbugs target.

On Mon, Jul 30, 2012 at 10:32 AM, Radim Kolar <hsn@filez.com> wrote:
> was any decision about findbugs made? you do not consider code style
> recommended by findbugs as good practice which should be followed?
>
> I can submit few findbugs patches, but it will probably turns into flamewar
> WE vs FINDBUGS like there:
> https://issues.apache.org/jira/browse/HADOOP-8619
>
> findbugs problems are pretty easy to fix and there are just 70 of them, it
> could be done in two days.
>
> I do not care about findbugs+cas-dev issue much because i need to fork
> cassandra anyway to get performance patches there. Its just matter of
> schedule for me if 1 should feed you fb patches before i fork it.