Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 7172401c2e38219e67daaa2acfbb685e7d7ee9cc
commit7172401c2e38219e67daaa2acfbb685e7d7ee9cc[log] [tgz]
authorAllen Hair <allenhair@google.com>Tue Mar 22 18:06:16 2022 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Tue Mar 22 18:06:16 2022 +0000
tree258808be86a09a107868fc1be7ea14d91e381518
parent1909adab99bcfdd0e9a7a6bdfc5169646756f3fa [diff]
parent9aae29f569377f57550cb8bf40fceb523a1f36bb [diff]
Merge "Update asm-7.0 to asm-9.2." am: d0cac61878 am: 807c94ba9d am: 9aae29f569

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

Change-Id: I6a6d266aa95523706a0092136456023de88308e8
tree: 258808be86a09a107868fc1be7ea14d91e381518
  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.