Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 8a70ce90323e75b63bd0eedd582a41557afe7ca2
commit8a70ce90323e75b63bd0eedd582a41557afe7ca2[log] [tgz]
authorGurpreet Singh <gurpreetgs@google.com>Thu Mar 23 11:33:37 2023 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Thu Mar 23 11:33:37 2023 +0000
tree1ac731fef973a6c5ac0db1533cde2501801440cb
parent3a9cfa5742eaaab14c820b36b115b2c936f54862 [diff]
parentd884ae3cc6669acd72dfc983e95a7c91a56e07db [diff]
Create metadata json file for each module am: 653f881161 am: d884ae3cc6

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

Change-Id: Ic30392b0369fd89dc6a0b2ea184a275077c77f95
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.