Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / packages / modules / common / 41c9d4dbaf30b54707bb2c220c8fd8c7fc21921f
commit41c9d4dbaf30b54707bb2c220c8fd8c7fc21921f[log] [tgz]
authorPaul Duffin <paulduffin@google.com>Thu Feb 10 15:13:12 2022 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Thu Feb 10 15:13:12 2022 +0000
tree82a1191dbb02d17cf87d7ba1ea0829ab1b610e16
parent8cff387be92da490e5873882a5b4184cc8d15b75 [diff]
parent54854ab89cfb5c6f690b65cb52318d1bbe217295 [diff]
Merge "Support building build target specific snapshots" am: 27aef8152b am: 6cf95bfc87 am: 54854ab89c

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

Change-Id: Ib63e62bffe7b1c29e5e4a5a953a7ab160d1bc463
tree: 82a1191dbb02d17cf87d7ba1ea0829ab1b610e16
  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.