I work with a large codebase split into many (~50) Eclipse projects. Attempting to scan the codebase triggers an individual scan of each project. All scans will attempt to run in parallel, bringing Eclipse/the computer to its knees.
The only workaround I'm aware of is to manually queue up scans of a couple projects at a time, waiting for each batch to mostly be finished before starting the next. This is quite tedious, and although Eclipse/the computer remains relatively responsive, I cannot make much use of the responsiveness because I'm busy watching progress bars and queueing up scans.
A theoretically simple solution would be for the FindBugs Eclipse plugin to queue scans, only running x at a time instead of attempting to run them all in parallel. Ideally, this limit x would be configurable in the plugin settings.
A likely more complex solution would be to somehow merge all the projects into a single scan task and run that. This may be more efficient due to not repeatedly scanning files referenced across projects, especially commonly used library classes.
