Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 56b37d65966947b117573821fb6d0755fa98474c
commit56b37d65966947b117573821fb6d0755fa98474c[log] [tgz]
authorNeha Pattan <npattan@google.com>Wed Mar 29 00:58:33 2023 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Wed Mar 29 00:58:33 2023 +0000
treed583463652f63793f9644a8c89a92783725017df
parentbe8e87e4bc130611a3afd7b07a7b43c832f79de1 [diff]
parent093fd21e0963c551f9ec51a024e28fd3eacc1653 [diff]
Merge "Rb: Integrate with AppSearch to persist consent data post-OTA." into tm-mainline-prod am: 0cafe40cc5 am: 093fd21e09

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

Change-Id: Ib89ee571d88682d9755a7bb830aba77ef0b2b26b
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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.