diff options
| author | Pete Gillin <peteg@google.com> | 2018-08-16 19:28:38 +0100 |
|---|---|---|
| committer | Pete Gillin <peteg@google.com> | 2018-10-29 16:02:51 +0000 |
| commit | 600c7cf83a183580e62864f5ba467ee90ab65f39 (patch) | |
| tree | c07f88662d68676ea929011430e3fde74fc114b7 /annotations/generate_annotated_java_files.py | |
| parent | 928653f71ea9c3467997a31acbef849f600f6793 (diff) | |
Turn on validation of nullability annotations for libcore.
This new target enforces that there are no broken annotations (e.g. on
primitive types) and that the missing annotations match the checked-in
warnings file.
This means that anyone checking in some new API surface in a class
which is otherwise annotated must either annotate it, or update the
checked-in warnings file. The latter option is as simple as making the
update target. (The error message contains these instructions.)
Bug: 73448108
Test: `make core-current-stubs-nullability-validation`
Test: `make core-current-stubs-nullability-validation-check-nullability-warnings`
Test: Change something, then `make core-current-stubs-nullability-validation-update-nullability-warnings`
Change-Id: I7ce044631ea144c83bd7ddefb9580bcb08b32a8b
Diffstat (limited to 'annotations/generate_annotated_java_files.py')
0 files changed, 0 insertions, 0 deletions