Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 19af87e3e6d7be57f3ecd75a877dfaad0f9c6537
commit19af87e3e6d7be57f3ecd75a877dfaad0f9c6537[log] [tgz]
authorHai Zhang <zhanghai@google.com>Tue Oct 05 18:49:10 2021 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Tue Oct 05 18:49:10 2021 +0000
tree03ca3290cde8088a483c3ce171ab76653c03d118
parente8e98efe4bca0c02d00e18c326ac080aadaa6bbc [diff]
parent393a1ca321b09d5599ee565217c9cac5d55d4932 [diff]
Add defaults for optimizing system server java_sdk_library. am: 393a1ca321

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

Change-Id: Ibf9bc06cdb68174a9f844a0f735fe72b8fe78826
tree: 03ca3290cde8088a483c3ce171ab76653c03d118
  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.