On 9 Mar 2013, at 19:01, Jonathan Gibbons <jonathan.gibb...@oracle.com> wrote:
> On 03/09/2013 12:11 AM, Chris Hegarty wrote: >> >> Everyone seems to agree, a solution needs to be found to allow us to keep >> certain areas warning free. This issue is too important, and too much time >> was spent, to allow it to regress to the state it was in a few years ago. > > It is true that selective use of -Werror does not play well with the new > build and the desire to compile as much as possible at any time, possibly > using sjavac. > > I have previously reported on a utility I've written in the past to analyze > java code and report on the different types of warnings found in different > packages. I'm sure we could take something like that utility and improve it > to the point where it can give errors when entries in the matrix which should > be empty are not. > > This utility could be run as a "test" meaning it needn't break the build but > the info is available for those that want to run it. Sounds interesting Jon, and certainly worth exploring. Another idea, is to enable all lint options and -Werror ;-) If the SuppressWarnings annotation was allowable on the PACKAGE Target :-^ It may be reasonable to add to the packages where applicable. -Chris. > > -- Jon
