Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 3f86c17842f2353d787a03b1a332602aa20e3693
commit3f86c17842f2353d787a03b1a332602aa20e3693[log] [tgz]
authorGurpreet Singh <gurpreetgs@google.com>Thu Mar 23 12:16:39 2023 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Thu Mar 23 12:16:39 2023 +0000
tree1ac731fef973a6c5ac0db1533cde2501801440cb
parent5e1bcf19cef4018517284578b8874aa5f5660aed [diff]
parent63935cfa88e6cb76da719c57c71c86974e07d688 [diff]
Create metadata json file for each module am: 653f881161 am: cbf04b22c8 am: 4880cd484a am: 63935cfa88

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

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