I'm actually of the fast fail preference, but unfortunately there are a couple of warning cases where suppression doesn't work.
By design, any call to a "sun" class spits out a Sun proprietary API warning with deliberately no way to turn it off. Importing a deprecated class causes a deprecation warning that no suppression annotation will remove, at least for the standard sun/oracle command line javac (some IDEs will remove it, and I've not tested with Java 7). We treat compiler warnings just like findbugs, PMD, etc. warnings, and acknowledge that there are some "false positive" cases that need to be ignored. -Spencer --- On Tue, 9/6/11, Luke Daley <[email protected]> wrote: I'm not aware of any situation where a warning can't be suppressed with @SuppressWarnings, but I don't have a lot of experience with it. The problem I am trying to address is that the build currently emits quite a few warnings and has done for a while. I'd prefer that it didn't.
