Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / e3e14c0ff155104dbe0081ee2736c72eb927a116
commite3e14c0ff155104dbe0081ee2736c72eb927a116[log] [tgz]
authorXin Li <delphij@google.com>Wed Oct 06 22:54:09 2021 +0000
committerXin Li <delphij@google.com>Wed Oct 06 22:54:09 2021 +0000
tree03ca3290cde8088a483c3ce171ab76653c03d118
parent393a1ca321b09d5599ee565217c9cac5d55d4932 [diff]
parent19af87e3e6d7be57f3ecd75a877dfaad0f9c6537 [diff]
Merge Android 12

Bug: 202323961
Merged-In: Ibf9bc06cdb68174a9f844a0f735fe72b8fe78826
Change-Id: I09f071b248cc973a64cce70c6a60e23f49f304e0
tree: 03ca3290cde8088a483c3ce171ab76653c03d118
  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.