Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 18e666b0969c88677ec381a0355a9411a9917d20
commit18e666b0969c88677ec381a0355a9411a9917d20[log] [tgz]
authorJeffrey Vander Stoep <jeffv@google.com>Tue Jan 17 18:51:24 2023 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Tue Jan 17 18:51:24 2023 +0000
tree120899cad23a78f6b6a8eba0f6cfb0ad11b14077
parentd2e3e30c70d1bc48f07dbbfd51329e7f3619569a [diff]
parentedc170a8889f742c5c193963a567a0cd034c3295 [diff]
Merge "Add libstatic_assertions." am: edc170a888

Original change: https://android-review.googlesource.com/c/platform/packages/modules/common/+/2362430

Change-Id: I83799eb9cc716b398bd0fdc8332bddf3e5db1485
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: 120899cad23a78f6b6a8eba0f6cfb0ad11b14077
  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.