Checker Framework 1.9.8

Version 1.9.8, 9 November 2015

Field initialization warnings can now be suppressed for a single field at a
time, by placing @SuppressWarnings("initialization") on the field declaration.

Updated Maven instructions to no longer require a script.
Added an example of how to use the instructions under
checker/examples/MavenExample.

The javac_maven script (and batch file) are deprecated and will be
removed as of December 2015.

Fixed issues: 487, 500, 502.

Checker Framework 1.9.7

Version 1.9.7, 24 October 2015

Fixed issues: 291, 474.

Checker Framework 1.9.6

Version 1.9.6, 8 October 2015

Fixed issue: 460.

Checker Framework 1.9.5

Version 1.9.5, 1 September 2015

Test Framework Updates:

• The test framework has been refactored to improve extensibility.
• Tests that previously extended ParameterizedCheckerTest or
  CheckerTest should extend either CheckerFrameworkTest or nothing.
• If a test used methods that were previously found on
  CheckerTest, you may find them in TestUtilities.

Fixed issues: 438, 457, 459.

Checker Framework 1.9.4

Version 1.9.4, 4 August 2015

Documented the notion of a compound checker, which depends on other checkers
and automatically runs them.

Renamed -AuseConservativeDefaultsForUnannotatedSourceCode command-line
option to -AuseSafeDefaultsForUnannotatedSourceCode

Moved the Checker Framework version control repository from Google Code to
GitHub, and from the Mercurial version control system to Git. If you have
cloned the old repository, then discard your old clone and create a new one
using this command:
git clone https://github.com/typetools/checker-framework.git

Fixed issues: 427, 429, 434, 442, 450.

Checker Framework 1.9.3

Version 1.9.3, 1 July 2015

New command-line options:

• -AsafeDefaultsForUnannotatedBytecode causes a checker to use conservative
  defaults for .class files that were compiled without running the given
  checker. Without this option, type-checking is unsound (that is, there
  might be errors at run time even though the checker issues no warnings).
• -AuseConservativeDefaultsForUnannotatedSourceCode uses conservative
  annotations for unannotated type uses. Use this when compiling a library in
  which some but not all classes are annotated.

Various bug fixes and documentation improvements.

Fixed issues: 436.