Android: Use a unified lint target
Lint is no longer implicitly run as part of an apk or bundle target. If a specific apk or bundle wants to turn on its own lint and have that run automatically on every build, the enable_lint flag can be used. See: "boundary_interface_example_apk". A new target //chrome/android:android_lint (or simply "android_lint") has been added. This currently runs either monochrome_public_bundle's lint task or a list of default targets if such a list is defined. For chrome apk/bundle targets based on chrome_public_apk_tmpl.gni, they will automatically get a data_dep added on the new unified lint target so most devs' workflow will not need to change. APKs in for {remoting,cronet,cast} have enable_lint added explicitly in this CL to preserve their existing behaviour. NewApi and VisibleForTests checks have been disabled for test apks, with a TODO for turning at least NewApi back on. Bug: 1108791 Fixed: 1108791 Change-Id: I6534fcd6dc7af1d7a12720a98f8d0d09bee8f161 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318549 Commit-Queue: Peter Wen <wnwen@chromium.org> Reviewed-by:Paul Jensen <pauljensen@chromium.org> Reviewed-by:
Lambros Lambrou <lambroslambrou@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Auto-Submit: Peter Wen <wnwen@chromium.org> Cr-Commit-Position: refs/heads/master@{#792728}
Showing
Please register or sign in to comment