Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of jukka.zitting@gmail.com
 designates 209.85.212.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4FBCD4D2.3030600@gmx.de>
References: <20120523120610.4ECC023889BF@eris.apache.org>
 <4FBCD4D2.3030600@gmx.de>
From: Jukka Zitting <jukka.zitting@gmail.com>
Date: Wed, 23 May 2012 14:55:41 +0200
Message-ID: 
 <CAOFYJNbLHgRmzD6szYrR18S6mqXQZDsBoAP3fmBa0P-wOQaQQw@mail.gmail.com>
Subject: Re: findbugs
To: oak-dev@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

On Wed, May 23, 2012 at 2:15 PM, Julian Reschke <julian.reschke@gmx.de> wro=
te:
> ...with the change below, findbugs can be run in oak-jcr with
>
> =A0mvn findbugs:findbugs
>
> ...leaving an XML file in ./target. There's also
>
> =A0mvn findbugs:gui
>
> for those who prefer point-and-click.

Nice!

Do we really need a SNAPSHOT version of the FindBugs plugin, or is the
latest release good enough?

> Should we add this globally?

Sounds like a useful thing to have, so +1 to adding it to the parent POM.

Did you already figure out a way for us to integrate FindBugs checks
to to the test phase of the build so we could fail the build if
explicitly enabled FindBugs checks fail?

BR,

Jukka Zitting