Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / dc5397b0c42f0a9dcf09791dc6c07c97b36bdf76
commitdc5397b0c42f0a9dcf09791dc6c07c97b36bdf76[log] [tgz]
authorPresubmit Automerger Backend <android-build-presubmit-automerger-backend@system.gserviceaccount.com>Fri Mar 24 18:06:57 2023 +0000
committerPresubmit Automerger Backend <android-build-presubmit-automerger-backend@system.gserviceaccount.com>Fri Mar 24 18:06:57 2023 +0000
treed583463652f63793f9644a8c89a92783725017df
parent12f919f8d565e8bfc9d0c1e665561b9c9cbd238d [diff]
parentd9a9f3f7e99a3f262d960fe823abaa0b053952f8 [diff]
[automerge] Rb: Integrate with AppSearch to persist consent data post-OTA. 2p: d9a9f3f7e9

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

Bug: 263297331
Change-Id: Idcd87ab18994ada040aab212a68fa3870c03568c
tree: d583463652f63793f9644a8c89a92783725017df
  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.