#1090 GUI shows less issues than exported XML

closed-invalid
5
2012-06-15
2012-06-14
No

I'm using the FindBugs plug-in 2.0.1-dev-20120614-r14386 with Eclipse Indigo SR2 (I also did try the current stable FindBugs plug-in previously). When running the analysis from the Package Explorer, only 6 issues are found. That is far less than what our FindBugs plug-in for Jenkins-CI is finding. I suspected different FindBugs configurations at first, but then it turned out that if I "Open Analysis Results in Editor" I also see way more than 6 issues in the XML file. It seems the XML file is not parsed correctly and the issues are not correctly display in the GUI.

Unfortunately, I'm not able to publicly upload the analysis report here.

Discussion

  • Please provide a reproducible small example, but I guess during the preparation you will notice that the bugs which were not shown has a low confidence/bug rank. Turning both options to the extreme in the Eclipse preferences you will see that the bugs are shown in the UI too.
    Regards,
    Andrey

     
    • status: open --> closed-invalid
     
  • You're right, it turned out to be a rank / confidence tuning issue. I was not aware that the GUI in fact filters the results form the XML. I thought the GUI settings are passed to FindBugs, which produces the XML, and all XML results are displayed.

    The way it currently works makes it hard to e.g. use the same FindBugs configuration locally as on a Jenkins-CI server. However, that is a different issue, and I'm closing this one.