Hi Jim,
If you can still reproduce the original problem, can you try
launching Eclipse from the command line and seeing if any
exception stack traces are printed to System.out or System.err?
I'm thinking that the Eclipse plugin got into a wedged state
due to an internal error in FindBugs.
The number of warnings produced shouldn't be an issue per se,
although the analysis can require a large amount of memory, so
you might want to try increasing the heap size (512M or more
is usually adequate for very large code bases).
-Dave
On Thu, Jul 15, 2004 at 11:29:31AM -0500, Jim Elliott wrote:
> Here's an interesting update...
>
> After plugging onward and fixing more of the bugs (in our own code)
> reported by FindBugs, it has started working again. I can see the "Find
> Bugs" option in the Java project context menu, and the pane has
> reappeared in the project properties, allowing me to adjust behavior.
>
> Perhaps the plugin was somehow getting overwhelmed by the number of
> things it was trying to report?
>
> -Jim
> _______________________________________________
> Findbugs-discuss mailing list
> Findbugs-discuss@xxxxxxxxxxxxxxxx
> http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss
|
