diff options
| author | 2023-11-02 11:29:49 +1100 | |
|---|---|---|
| committer | 2023-11-03 11:44:22 +1100 | |
| commit | 21a709f4f3182aee9be1469af45c16192cb50868 (patch) | |
| tree | c46ca41ca03c53e0adfcfb9dd3d5c462beebd2ab | |
| parent | c018edbdad81e8f4efa41a77f56d66d536e123bf (diff) | |
lint: update documentation on how to update the baseline
It is possible to simply pass the `nowarn` flag to Soong via Android.bp
instead of modifying Soong itself.
Bug: 220214993
Test: n/a
Change-Id: I38a3cfbe3b6d9ad144f13d53da85bb47475e75bd
| -rw-r--r-- | tools/lint/README.md | 13 |
1 files changed, 9 insertions, 4 deletions
diff --git a/tools/lint/README.md b/tools/lint/README.md index b235ad60c799..ff8e44229189 100644 --- a/tools/lint/README.md +++ b/tools/lint/README.md @@ -103,10 +103,15 @@ out/soong/.intermediates/frameworks/base/services/autofill/services.autofill/and As noted above, this baseline file contains warnings too, which might be undesirable. For example, CI tools might surface these warnings in code reviews. In order to create this file without -warnings, we need to pass another flag to lint: `--nowarn`. The easiest way to do this is to -locally change the soong code in -[lint.go](http://cs/aosp-master/build/soong/java/lint.go;l=451;rcl=2e778d5bc4a8d1d77b4f4a3029a4a254ad57db75) -adding `cmd.Flag("--nowarn")` and running lint again. +warnings, we need to pass another flag to lint: `--nowarn`. One option is to add the flag to your +Android.bp file and then run lint again: + +``` + lint: { + extra_check_modules: ["AndroidFrameworkLintChecker"], + flags: ["--nowarn"], + } +``` # Documentation |