Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 807c94ba9d82eae069b02c622094dfa3ceb9a72b
commit807c94ba9d82eae069b02c622094dfa3ceb9a72b[log] [tgz]
authorAllen Hair <allenhair@google.com>Tue Mar 22 17:20:25 2022 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Tue Mar 22 17:20:25 2022 +0000
tree81e8afc292252867ceaa4244fcde2fb41a62c1cd
parentca43b52c8f5b301f0fded07fdd37fb5ea5ecdb64 [diff]
parentd0cac618782ac3de3e9c21b1694a2d786b331505 [diff]
Merge "Update asm-7.0 to asm-9.2." am: d0cac61878

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

Change-Id: I844f5f28268fe68de8cb93f14199779cf3274d67
tree: 81e8afc292252867ceaa4244fcde2fb41a62c1cd
  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.