Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.0.0-alpha1
-
None
-
None
Description
Currently test-patch.sh uses OK_JAVADOC_WARNINGS to know how many warnings trunk is expected to have. However, this is a fragile and difficult to use system, since different build slaves may generate different numbers of warnings (based on compiler revision, etc.). Also, programmers must remember to update OK_JAVADOC_WARNINGS, which they don't always. Finally, there is no easy way to find what the new javadoc warnings are in the huge pile of warnings.
We should change this to work the same way the javac warnings code does: to simply build with and without the patch and do a diff. The diff should be saved for easy perusal. We also should not complain about warnings being removed.