Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / b3f8ed74cba9e98c4f4c9444d77c05f1564825e9
commitb3f8ed74cba9e98c4f4c9444d77c05f1564825e9[log] [tgz]
authorMartin Stjernholm <mast@google.com>Tue Mar 29 09:59:26 2022 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Tue Mar 29 09:59:26 2022 +0000
treea2f129e29c5ab7f24d49b8e0836a673aeeabd63f
parent139f30cff541cc699127107b5950ced20f333eeb [diff]
parent8fa5ddae14c69a06ebb1f13ba5b26f8721be02bf [diff]
Merge changes I8bc68d10,Ie6182fa4 am: 8fa5ddae14

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

Change-Id: Ia46c9466fdd242f69bec23b39006e09d82eeaa3e
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: a2f129e29c5ab7f24d49b8e0836a673aeeabd63f
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. generate_ml_bundle.sh
  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.