Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 8f3c2f946ba41ddab380b76cc00a940049cca5db
commit8f3c2f946ba41ddab380b76cc00a940049cca5db[log] [tgz]
authorAnton Hansson <hansson@google.com>Fri Apr 29 11:34:34 2022 +0000
committerAnton Hansson <hansson@google.com>Fri Apr 29 11:40:42 2022 +0000
treec8d3d0920ddd87b1a40d75889b06aa59f2395b0f
parent018e0d0f5403ec76f2f2a1035b099014ec442f10 [diff]
Default-on strict updatability linting for Modules

Modules should be enabling this by now.

Test: errorprone build
Change-Id: I04efcf5b8903c50289809fc8e97d002d81e4754e
1 file changed
tree: c8d3d0920ddd87b1a40d75889b06aa59f2395b0f
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. generate_ml_bundle.sh
  9. MODULES_OWNERS
  10. OWNERS
  11. PREBUILTS_MODULE_OWNERS
  12. PREUPLOAD.cfg
  13. README.md
README.md

packages/modules/common

This project includes mainline build and other utility code. Any library code intended for use by modules should go in frameworks/libs/modules-utils instead.

java code

This project uses a single source path for java code. All java code should go in the java directory with subdirectories corresponding to the java package. Android.bp files should go alongside the java source files, and should only include java source for a single java package to encourage good code hygiene.

Tests for java code should go in the javatests directory and follow the same structure.