Guys `n' dolls, One if the new tools for maintaining our quality is the new job slowbuild. It does a build and then runs findbugs (and other tools) against our code base. Since a while this has been going on and it succeeds if no new warnings where introduced since last successful build. For a while now it has been failing.
Committers please check the results of this build, especially after you committed a contribution. You can not foresee all errors but findbugs is a wonderful tool for warning against harmful coding patterns. I've seen people addressing issues at will and this is great. We had a session to mitigate the issues revealed by findbugs and found that they had a good effect on code quality after getting over the initial unexpected side effects. So I want to invite everybody to once in a while triage some issues from that list at will. Expect to hunt after unwanted effects of your fixes! This is not true for newly introduced warnings. These should be easily fixed. Kind regards, -- Daan
