Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / d9a9f3f7e99a3f262d960fe823abaa0b053952f8
commitd9a9f3f7e99a3f262d960fe823abaa0b053952f8[log] [tgz]
authorNeha Pattan <npattan@google.com>Fri Mar 24 15:56:29 2023 +0000
committerNeha Pattan <npattan@google.com>Fri Mar 24 18:06:12 2023 +0000
tree8348d25df1651e6aafa1d97fe45da0f0e1514f6c
parentb9879e81a6c26174e77f815e775e49f2877f7f0c [diff]
Rb: Integrate with AppSearch to persist consent data post-OTA.

Bug: 263297331
Test: atest and manual
Previous-Platform-Support: AppSearch was not used by Rb before this
Test-Info: same as above
Aosp-First: not ready for AOSP
Ignore-AOSP-First: not ready for AOSP
Apex-Size-Increase: 86kB
Change-Id: I8a925cada497805fb64ac3346b33359cab9c3b83
1 file changed
tree: 8348d25df1651e6aafa1d97fe45da0f0e1514f6c
  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.