YouTube Movie: Taking FindBugs in NetBeans IDE for a Spin

Didn't know the first thing about FindBugs in NetBeans IDE when I started making this movie, as you'll see. Bear with me to the end and you'll learn what I did.


Not being able to run FB on suite project - because it has no Java sources. Only the modules in the suite have Java sources. If you want to analyze them all, open them all and set the scope to Open Projects. Yes the UI should show a warning when you try to run an inspection on a project with no source roots; I asked for something similar (w.r.t. Analyze Javadoc) in #203134 but this was rejected. #210465 might also enable the analyzer to determine that the user meant to scan submodules.

Posted by Jesse Glick on April 24, 2012 at 01:28 PM PDT #

Note that if you add Common Annotations API to classpath of a module, the hint "suppress warning" on FB warnings will work. (Unfortunately java.lang.SuppressWarnings cannot be used for bytecode-based tools.)

You can also disable detectors which you know will be irrelevant to your app, such as those relating to serialization.

Posted by Jesse Glick on April 24, 2012 at 01:47 PM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed

Geertjan Wielenga (@geertjanw) is a Principal Product Manager in the Oracle Developer Tools group living & working in Amsterdam. He is a Java technology enthusiast, evangelist, trainer, speaker, and writer. He blogs here daily.

The focus of this blog is mostly on NetBeans (a development tool primarily for Java programmers), with an occasional reference to NetBeans, and sometimes diverging to topics relating to NetBeans. And then there are days when NetBeans is mentioned, just for a change.


« April 2015