Sparked by Bill's talk at JavaOne, I started to look at running findbugs
over the jdk7 classes. Some of the issues I ran into:
* Performance is very very slow. It starts out using maybe 20-40% of
of CPU, then slowly gets to about 900MB in size (I gave it 1024Mb)
and slows down to about 1-4% of a CPU. This is on Solaris 10, X64
machine with 2cpus 2Gb ram.
Does anyone have any tricks to make findbugs run faster?
* When I tried to give it tools.jar, I got complaints about
missing classes, so I tried -auxclasspath, but eventually gave up.
Why would it not find classes that are normally in the JDK
boot classpath?
* I use findbugs in NetBeans all the time, but in this case I ran
findbugs from the command line and I saw errors related to the
spelling of a method name not starting with a lowercase character.
I'd never seen that error before, and it doesn't strike me as a
real coding "error" at all. Most findbugs errors I have seen in the past
were really valid problems in the code, not style issues.
Could I be getting some contributed findbugs modules by using the
command line? Coding style checking really isn't that important and
it's quite possible in the JDK that I could never change the method
spelling anyway.
-kto
_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@...
https://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss
