Java – findbugs and Google codepro Analytix (Eclipse Plug-in)

I've used Google codepro Analytix, but I've never used findbugs

Findbugs' first impression is that configuration is more difficult After that, I believe both are similar@ H_ 301_ 3@

What do you think@ H_ 301_ 3@

Another related problem: none of these plug-ins send our code to the server, right? (for example, if we use codepro, our code will not be sent to Google server)@ H_ 301_ 3@

Solution

Update 2016: codepro Analytix is no longer available, so go with findbugs

Original answer @ h_ 301_ 3@

Better in codepro Analytix: @ h_ 301_ 3@

>The problem level (error, warning, information) can be changed for each item Findbugs can only enable / disable problems. > Many problems can be configured in detail (such as blacklisted swearing words). > All problems in the currently open editor can be displayed (and adjusted when opening or closing the editor), so that it is more convenient to select software packages, projects or other operations, and then manually trigger their scanning > several problems can be repaired automatically (such as the final declaration of all parameters) In findbugs, everything must be done manually@ H_ 301_ 3@

Better at findbugs: @ h_ 301_ 3@

>More focus on typical Java programming errors (but there are no rich selection problems, such as codepro) > do more analysis and need a lot of context information > can be used on eclipse or local integration server, such as Hudson / Jenkins > the configuration in Hudson / Jenkins and local ide can be shared, Therefore, you can see exactly the same results on IDE and server > there is a "cloud model", and distributed teams can share their findings (and evaluation results) so that they won't check the same problem again @ H_ 301_ 3@

All of the above is more relevant to how you use the tool The actual discovery of errors can be very dependent on the item to be checked In the past, I often suggested using findbugs first, and then codepro: @ H_ 301_ 3@

First check with findbugs because it found more serious problems However, after modification, you may find that you have many noisy problems (or even wrong findings) Therefore, after dealing with the most difficult findbugs problem, I suggest switching to codepro Analytix because it has less error discovery and can be controlled in more detail@ H_ 301_ 3@