#1083 FB eclipse error "no analysis passes"

Core (142)

Using MyEclipse 9.1 and FB plugin version

I was trying to set a project's FB settings such that it would not report any errors in a project. The attachments show the FB settings for the project. This is the error I get when FB runs on that project.

java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -showlocation
Command-line arguments: -os win32 -ws win32 -arch x86_64 -showlocation

Wed May 30 16:22:59 EDT 2012
An internal error occurred during: "Finding bugs in tms-core...".

java.lang.AssertionError: no analysis passes
at edu.umd.cs.findbugs.FindBugs2.analyzeApplication(FindBugs2.java:1063)
at edu.umd.cs.findbugs.FindBugs2.execute(FindBugs2.java:278)
at de.tobject.findbugs.builder.FindBugsWorker.runFindBugs(FindBugsWorker.java:314)
at de.tobject.findbugs.builder.FindBugsWorker.work(FindBugsWorker.java:222)
at de.tobject.findbugs.builder.FindBugsBuilder$StartedFromBuilderJob.runWithProgress(FindBugsBuilder.java:210)
at de.tobject.findbugs.FindBugsJob.run(FindBugsJob.java:102)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


  • Scott Hamilton

    Scott Hamilton - 2012-05-30

    FindBugs project settings files

  • Scott Hamilton

    Scott Hamilton - 2012-05-30
    • priority: 5 --> 2
  • Andrey Loskutov

    Andrey Loskutov - 2012-05-30

    Hi Scott,

    "I was trying to set a project's FB settings such that it would not report any errors in a project. "

    So *what* exactly you did?

    Can you also please attach your FindBugs settings for the project (.settings/edu.umd.cs.findbugs.core.prefs and .settings/edu.umd.cs.findbugs.plugin.eclipse.prefs).


  • Andrey Loskutov

    Andrey Loskutov - 2012-05-30

    Arrgh. Ignore my last comment. This crazy tracker... It is a real pain to use it after working with Jira/Bugzilla. I see the files now.

  • Andrey Loskutov

    Andrey Loskutov - 2012-05-30

    Well... According to the edu.umd.cs.findbugs.core.prefs, you've managed to disable each and every detector. WHY??? Without a single detector FB analysis will be just ... empty. Surprise surprise :-)
    So I tend to close this issue as invalid.
    Any comments on that?

  • Andrey Loskutov

    Andrey Loskutov - 2012-05-31
    • status: open --> pending-invalid
  • Scott Hamilton

    Scott Hamilton - 2012-05-31


    As you probably saw, I set the priority on this to low... this is not something I expect would be encountered by many. What we were doing here is establishing a baseline to see how fast the scanner would complete with no detectors, then were going to measure the performance of adding in specific other detectors.

    I debated logging this bug but figured that the fact that it did generate an error dialog and stack trace in the log could possibly point to an issue that might be visible under other conditions.

    I have no problem about declaring this invalid if that cannot be the case.

  • Andrey Loskutov

    Andrey Loskutov - 2012-05-31
    • labels: 840439 --> Core
    • assigned_to: andyandy --> wpugh
    • status: pending-invalid --> pending
  • Andrey Loskutov

    Andrey Loskutov - 2012-05-31

    Hi Bill,
    what do you think?
    Is it a valid expectation that FB can run without a single detector?

  • J.C. Hamlin

    J.C. Hamlin - 2012-09-27

    It should still run with no detectors enabled without failing. For those of us that want to do performance measurements of the detectors speed on our code, having a baseline with no detectors enabled (to just find the overhead of the reading/loading/parsing of the bytecode) is an important baseline measurement so we can then start seeing how long each detector actually takes by determining how much time that detector adds to the total.

  • Graham Allan

    Graham Allan - 2012-12-10
    • status: pending --> closed-wont-fix
  • Graham Allan

    Graham Allan - 2012-12-10


    I have worked around the exception thrown by FindBugs to allow the behaviour you're looking for. That is, to implement a no-op plugin detector, which will avoid the exception, but will not perform any analysis, thus allowing performance measurements to be taken. The no-op plugin detector is available here: https://github.com/Grundlefleck/no-op-findbugs-detector

    I have taken the liberty of closing off this issue, hope that;s okay.

    ~ Graham


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks