[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [eclipse.org-architecture-council] FindBugs
|
Agree,
what we need is not a "best practice to use FindBugs" but
some recommended best practice on "how to use
FindBugs".
Should it be part of nightly builds?: Should developers use
it? What are good default settings? How to share customized default settings in
the team? How to mark false positives that have been investigated, such that
they are not reported again (for anyone on the team)?
The last question is the one most near and dear to me, and
I have requested a feature similar to API Tooling Problem
Filters:
I understand that some improvements have been made along
those lines but both requests are not quite done yet.
Cheers,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management Project
Lead, DSDP PMC Member
eclipse.org-architecture-council-bounces@xxxxxxxxxxx wrote on
06/05/2009 02:27:58 PM:
> Does anybody on the AC have experience with
FindBugs that they'd care to
> share?
I have used
FindBugs and was impressed by the high signal to noise ratio. You can also
configure it to only report new issues that have been introduced since a
certain baseline. That way, you can avoid having to look through false
positives more than once.
> I'd like the AC to consider
making the use of FindBugs a best practice
> recommendation for
projects.
Makes sense to
me.
Boris
