Geertjan's Blog

  • May 3, 2012

NetBeans IDE 7.2: FindBugs Integration

Geertjan Wielenga
Product Manager

Silent movie, 1 1/2 minutes in length.

Join the discussion

Comments ( 14 )
  • Gualtiero Thursday, May 3, 2012


    nice feature. Can you explain the difference with SQE plugin which I'm already using in 7.1 ?



  • Jesse Glick Thursday, May 3, 2012

    More interesting is showing how to evaluate warnings quickly and either fix them (if real bugs) or suppress them (if not).

  • icarus Friday, May 4, 2012

    Do I need a plugin to use this feature? I have a clean install of Netbeans 7.1.2 and can't find this feauture.

  • Geertjan Friday, May 4, 2012

    Please read the subject line of this blog entry again. It says 7.2. That's why you can't find anything about it in 7.1.2, because it is part of the next release.

  • Brett Ryan Wednesday, May 9, 2012

    Hi Geertjan, I as Gualtiero am also curious, do we no longer need to install the SQE plugin for FindBugs support? Does NB7.2 also come with PMD support?

    I'm also interested if the plugin behaves the same as the SQE one, for me at least it doesn't seem to recognise when I turn off rules or when I select the ignore function from the gutter menu. Also I haven't (yet) found a way to clear all findings from the editor windows. Have these been addressed in the integrated version?

  • guest Wednesday, May 9, 2012

    Will there be option to synchronize "false positives" with i.e. Sonar?

  • Pavel Cibulka Thursday, May 10, 2012

    Is it Findbugs 2.0 or some older version? Also +1 for Checkstyle and PMD integration.

  • Henrik Sunday, July 1, 2012

    I can't get it to work :-(. In both 7.2 Beta and RC 1 it basically finds nothing properly because no rules are active in the default setup.

    However when I try to define a strict setup and configure all the rules, it bombs out during inspection and sends a report to netbeans.org.

    Back to 7.1 for me

  • Geertjan Sunday, July 1, 2012

    So FindBugs is working for you in 7.1?!

  • guest Thursday, August 16, 2012

    Thanks for sharing this information, Geertjan! I'm wondering how a custom FindBug configuration could be distributed within a team of developers?

  • guest Sunday, October 14, 2012

    I applaud this work. However, this is a lot slower than the SQE plugin, and the UI is much, much harder to use. I am therefore going back to using SQE.

    a) The tree navigation to get to the actual bugs is 7 levels deep before I get to something clickable to jump to the source. In SQE, it's 3 or 4 levels, which is still too many. 2 would be appropriate. See the demo findbugs UI for a good example of how to categorize bugs.

    b) I don't seem to be able to scan and reload findbugs warnings for a single project, only for all open projects.

    c) I can't easily categorize bugs. By source package is a totally useless structure. I'd like them by bug type at top level, with the next level being instances of the bug.

  • Geertjan Sunday, October 14, 2012

    There's an icon in the Results window that lets you switch to a different view where the found bugs are categorized based on FindBugs categories. And if you have another look at the Inspect dialog, you'll see that you can set the scope.

  • Geertjan Sunday, October 14, 2012

    Sorry, I didn't mean Results window. I meant the Inspector Window. You'll find a button there with the tooltip "Categorize".

  • Jeremy Saturday, August 31, 2013

    Is there a site where there is discussion about this? I'd like the findbugs codes (e.g. WMI_WRONG_MAP_ITERATOR) to be displayed as well, and it would be nice if I could point to the same excludes file where I run findbugs nightly.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.