Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 43b864e47eebd8330fd1c44f642ca82f6170a03e
commit43b864e47eebd8330fd1c44f642ca82f6170a03e[log] [tgz]
authorXin Li <delphij@google.com>Tue Oct 17 10:08:58 2023 -0700
committerXin Li <delphij@google.com>Tue Oct 17 10:08:58 2023 -0700
treec7e1ddea97b03c8971598bde23a40ce6da377f4d
parent4671061908085a1582fdab1456ef789acdf8644e [diff]
parent4e7b1405be5462e466a294b7ed134de18b462947 [diff]
Merge 10952656

Merged-In: Ie9e51b38ecfed3db1735d73032fd49a3c5e07fc2
Change-Id: I3520485c96d72a5cf8f2a72b53fc341caa55d597
tree: c7e1ddea97b03c8971598bde23a40ce6da377f4d
  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.