Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 73e09b282a55fd643686e5d20a63dfa036c5db5d
commit73e09b282a55fd643686e5d20a63dfa036c5db5d[log] [tgz]
authorAurimas Liutikas <aurimas@google.com>Wed Aug 18 15:03:01 2021 -0700
committerColin Cross <ccross@android.com>Thu Sep 09 14:41:17 2021 -0700
treee986d3af7d969ea0ad1a0f6d1b5eda8b5bf1e27c
parent6d6909abebf99f23ee888cb1e6c132e100b9868c [diff]
Update apex allowed list

Test: N/A
Change-Id: Ib5f548e177d3a484dee64f368d566bbbc3076bab
Merged-In: Ib5f548e177d3a484dee64f368d566bbbc3076bab
(cherry picked from commit 0b577f961f7e3464793b5b0ca102d433191aab60)
1 file changed
tree: e986d3af7d969ea0ad1a0f6d1b5eda8b5bf1e27c
  1. build/
  2. java/
  3. proto/
  4. sdk/
  5. tools/
  6. Android.bp
  7. generate_ml_bundle.sh
  8. MODULES_OWNERS
  9. OWNERS
  10. PREBUILTS_MODULE_OWNERS
  11. PREUPLOAD.cfg
  12. 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.