Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 7a53f792da806d5f37ae9043cb83536e227d6a84
commit7a53f792da806d5f37ae9043cb83536e227d6a84[log] [tgz]
authorPaul Duffin <paulduffin@google.com>Wed Mar 30 17:46:05 2022 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Wed Mar 30 17:46:05 2022 +0000
treeba75d12ebcb700e35dab75e4023cd05f1bfd4c45
parent6d60c8bb589a34486b4ee5914d8c087381fd713e [diff]
parentfa90e1e5e0d2c0e4ded12d66cc6ac59b7db4e264 [diff]
mainline_modules_sdks.py: Fix issues with r snapshot am: fa90e1e5e0

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

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