search

ac1692 / google-collections

Automatically exported from code.google.com/p/google-collections
Apache License 2.0
0 stars 0 forks source link

Run static analysis tools #78

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
We should run static analysis tools, such as FindBugs, on the Google
Collections code and fix any valid issues that they uncover.

Original issue reported on code.google.com by jared.l....@gmail.com on 10 Jun 2008 at 7:03

GoogleCodeExporter commented 9 years ago 
The only issue here is settling on a tool and adopting its mechanism for 
suppression.
 Some require suppression via a comment or annotation in the code, and we'd have to
be willing to add those to our code.  Some may store it externally, in which 
case
we'd need to be able to include that external representation in our googlecode 
project.

I agree that in time for 1.0 we could make a one-off single pass through the 
code,
but post-1.0 something more durable will be needed.

Original comment by kevin...@gmail.com on 10 Jun 2008 at 7:14

GoogleCodeExporter commented 9 years ago 
I've been through the full findbugs report and found nothing serious.

Original comment by kevin...@gmail.com on 29 Dec 2008 at 8:44