Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / dac49bb65a8c76ff77e0f222101d9b6e150d138b
commitdac49bb65a8c76ff77e0f222101d9b6e150d138b[log] [tgz]
authorJingwen Chen <jingwen@google.com>Wed Mar 22 15:00:57 2023 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Wed Mar 22 15:00:57 2023 +0000
tree76b233e5ac0233af383d9f84b1893e13d318dd71
parent0b93f78b43bd949da48f78a25204cef06f994d05 [diff]
parent3a9cfa5742eaaab14c820b36b115b2c936f54862 [diff]
[conflict] Enable bazel in mainline build script. am: be577742a1 am: b9879e81a6 am: 3a9cfa5742

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

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