To run the Checker Framework, you need to use a JDK 17 or later version of javac. That is, you need to use JDK 17 or later when compiling your code.
The Checker Framework can type-check any Java project, including projects that compile to Java 8 or 11 bytecodes and run on JRE versions 8 or 11. That is, your code can run under any release of Java, from Java 8 onward.
The type qualifiers and utility libraries in checker-qual.jar and checker-util.jar still use Java 11 bytecode. Thus, they may be used in projects that run under Java 11 or later.
Since version 3.0.0, 91 authors have made over 4500 commits and closed over 600 issues. Thanks to everyone who contributed!
New checkers include:
ExecutionControl, file, FileLock, Formatter, reader, Scanner, socket, stream, writer, etc.New command-line arguments include:
-AskipFiles, -AonlyFiles-AassumeSideEffectFree, -AassumeDeterministic, -AassumePure, -AassumePureGetters-AuseConservativeDefaultsForUncheckedCode-AignoreRawTypeArguments-AwarnRedundantAnnotations-Ainfer=ajava, -AinferOutputDirectory, -AinferOutputOriginal, -AshowWpiFailedInferences-AshowSuppressWarningsStrings, -AwarnUnneededSuppressionsExceptions-AshowPrefixInWarningMessages-AstubNoWarnIfNotFound, -AstubWarnNote, -AmergeStubsWithSource-Aonelinemsg, -AdumpOnErrors, -AexceptionLineSeparator-ApermitMissingJdk, -AparseAllJdk-AslowTypecheckingSeconds-Aversion, -AprintGitPropertiesOther improvements include thousands of enhancements and bug fixes -- too many to list here.
All previously-deprecated methods and classes have been removed. If your project builds upon the Checker Framework, we suggest that you upgrade to version 3.55.1, resolve all the deprecation warnings, then upgrade to version4.0.0.