Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 6c81b86af0e8ea541c551793b00bda7f51225cfc
commit6c81b86af0e8ea541c551793b00bda7f51225cfc[log] [tgz]
authorXin Li <delphij@google.com>Tue Jun 28 13:28:32 2022 -0700
committerXin Li <delphij@google.com>Tue Jun 28 13:28:32 2022 -0700
treeb019e85128226ee546edcce795d44aa821bbfe94
parentadc570a3f3c6b8fba8ec629dc4e95a38fd559550 [diff]
parent4ccc7837cbb503ba552e105b0be485d7d67468fd [diff]
Merge tm-dev-plus-aosp-without-vendor@8763363

Bug: 236760014
Merged-In: I788f4287df2130750b32b9e07d73043ed1433c98
Change-Id: I59a87f4a7a2504d61c9b3e047952aecf916d5dc9
tree: b019e85128226ee546edcce795d44aa821bbfe94
  1. build/
  2. java/
  3. javatests/
  4. proguard/
  5. proto/
  6. sdk/
  7. tools/
  8. Android.bp
  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.