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

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

Change-Id: Ibb597c2e5f126eb15ed621913526dc973c69bb8c
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.