Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / c44a9cd835e606c30c9b0293c097d7a347387935
commitc44a9cd835e606c30c9b0293c097d7a347387935[log] [tgz]
authorPaul Duffin <paulduffin@google.com>Wed Mar 30 18:05:31 2022 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Wed Mar 30 18:05:31 2022 +0000
tree3439d9476dd2dc66e9b53dd044302218f2373a7a
parenta59448a48c7af1b26d44c536f2d9c0724ff7d81e [diff]
parent7a561d6ed15c6dbf46b282be9ba06d1f698e42b2 [diff]
mainline_modules_sdks.py: Reformat am: 2ef33a4d65 am: 7a561d6ed1

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

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