https://issues.apache.org/bugzilla/show_bug.cgi?id=46103
--- Comment #3 from [EMAIL PROTECTED] 2008-10-28 04:51:20 PST --- Thanks for the effort and thanks for sharing the results. You might wonder, why the use of such a sophisticated tool like JTest doesnt produce more 'sophisticated' bug-warnings: in the last two years the Batik code-base has been analysed from time to time with Findbugs and the detectors in the IntelliJ IDE. So most of the interesting (and mechanically findable) bugs have been found and removed already... The names of the authors show, that these are parts of Batik, which havent been touched since quite a while - 'stable code'. Most of the 'sync on non-final' - warnings are known to me - no urgent action needed. I'd prefer to make those fields final or private, but that changes the API of the class. I will have a look on those conditional expressions with fixed outcome. If you want to test the capabilities of your tool, you might try an older version of Batik - there have been some interesting bugs. OTOH, when you have a new, state-of-the-art detector waiting to see some non-trivial real world code, then Batik is the right food for it. greetings dieter von holten -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
