Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 192a2f60eedf89b2c9d870591e720706a2bbff1e
commit192a2f60eedf89b2c9d870591e720706a2bbff1e[log] [tgz]
authorMartin Geisler <mgeisler@google.com>Tue Feb 14 10:14:20 2023 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Tue Feb 14 10:14:20 2023 +0000
tree3958c2fae363faeb1f766818326daeb41b643c19
parent803afdea879618c1a07fdecfc0d0663d00225944 [diff]
parentb6cffd8a23239ff9d28cb5e2ecedce5a6a051ccd [diff]
Allow serde as a dependency of the bytes crate am: 3df37fb734 am: b6cffd8a23

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

Change-Id: I331e3f8767717ee0785a245c8a523a59e8abfe49
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: 3958c2fae363faeb1f766818326daeb41b643c19
  1. build/
  2. java/
  3. javatests/
  4. proguard/
  5. proto/
  6. sdk/
  7. tools/
  8. Android.bp
  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.