Automate (if possible) the verification of source rules, e.g. use of tabs etc.

Example was java/lang/String.java, where a mixture of spaces and tabs have crept
into the source file making it hard to view/edit.

Peabody users are finding it awkward editing some of the sources in the JDK due to
mixed uses of tabs and spaces.
If the build process included some kind of style or tab checking, resulting in build
warnings (yeah I know, we have lots of those already), then we could at least
police the issue. Not sure what other style issues we could police.

It would be important that these not result in complete build failure, but we do
need some way to make all the warning messages more visible, on all platforms, from all compilers, native and javac, and these warnings too...


###@###.### 2005-04-19 21:16:02 GMT