Hi all,
from my point of view, applying FindBugs to Jabaco.jar is a good idea. I tried the stand-alone Swing version of FindBugs. The list of findings is impressive.
However, it would be short-sighted to draw the direct conclusion "high number of errors = low quality of Jabaco". FindBugs is optimized to find potential problems in human-written code. Emphasis on "potential". Compiler-generated code might deliberately chose to use constructions which could be dangerous and difficult to maintain for typical developers.
The next step could be to cluster the warnings devised by FindBugs into severity levels. "real" problems should be solved, ideally by community volunteers. An excellent opportunity to get to know the Jabaco framework and to develop personal Java skills.
Best regards,
A1880