pivot-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Brown <gkbr...@mac.com>
Subject Re: FindBugs analysis before the 1.3 release
Date Fri, 31 Jul 2009 14:40:31 GMT
FYI, this belongs on pivot-dev, not pivot-private.

FindBugs seems to generate a lot of false positives. See if you can  
reduce the signal/noise ratio and let us know if there's anything in  
there that looks like it might be a real problem.


On Jul 31, 2009, at 10:36 AM, Sandro Martini wrote:

> Hi to all,
> I've done (another time) an analysis on sources from pivot Trunk with
> the latest FindBugs (this time inside eclipse, and finally directly
> connected to subversion  :-) ).
> As always (on any project !!) it has found some things, how / what can
> we do (i think open jira bugs for real things, but i hope not for
> simple bugs) ?
> Should we wait to fix the code freeze for the next release (1.3), or
> can we start now ?
> I'm sorry but FindBugs export results only in a
> development-pc-dependent way (absolute paths, etc), and
> not-so-readable without it.
> Some things have been already discussed with Greg last time, and in
> any case before spending time to do a patch, i discuss always with
> others.
> And to avoid confusion on subversion, would it be good to attach to
> pivot-dev source patches ?
> Bye,
> Sandro

View raw message