Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 4d6ca140280fce99613d2732762acd314eb74f56
commit4d6ca140280fce99613d2732762acd314eb74f56[log] [tgz]
authorPaul Duffin <paulduffin@google.com>Wed Mar 30 18:05:48 2022 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Wed Mar 30 18:05:48 2022 +0000
treea5bc71b4b5deb967f1f6c5ff83276fec81c6fcdf
parent19afde65a1c760955a2615e50a2970fbe8241082 [diff]
parentb419f5ca7ae2a8a23509ff69e8aa794b0be17e1e [diff]
Add test for snapshot build order am: ec1fdcdee4 am: b419f5ca7a

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

Change-Id: I1d6286e52cdbb82b6e21a3422d2e1be4f0dd4912
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: a5bc71b4b5deb967f1f6c5ff83276fec81c6fcdf
  1. build/
  2. java/
  3. javatests/
  4. proguard/
  5. proto/
  6. sdk/
  7. tools/
  8. Android.bp
  9. generate_ml_bundle.sh
  10. MODULES_OWNERS
  11. OWNERS
  12. PREBUILTS_MODULE_OWNERS
  13. PREUPLOAD.cfg
  14. 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.