Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 217c1e2abd7278d0ed9069d0a121d5b1d15ca44d
commit217c1e2abd7278d0ed9069d0a121d5b1d15ca44d[log] [tgz]
authorAdam Seaton <aseaton@google.com>Tue Jun 06 19:15:13 2023 +0000
committerAdam Seaton <aseaton@google.com>Thu Jun 08 16:10:10 2023 +0000
treece2691c50584c2f2fd6661685a1f739b41edf2a8
parent478c28bbc8aef1f5c621b79f28ff0ddb9557e317 [diff]
Fix OWNERS for prebuilt module drops Bug:286093002

Ignore-AOSP-First: Cherrypick to an older branch from AOSP.
Change-Id: Iabc9e1258ab25d357c4ba3f28169095ea881e9a9
Merged-In: dfddf6874671a70d54dc86ab8325772268deffca
1 file changed
tree: ce2691c50584c2f2fd6661685a1f739b41edf2a8
  1. build/
  2. java/
  3. javatests/
  4. proguard/
  5. proto/
  6. sdk/
  7. tools/
  8. Android.bp
  9. generate_ml_bundle.sh
  10. MODULES_OWNERS
  11. OWNERS
  12. PREBUILTS_MODULE_OWNERS
  13. PREUPLOAD.cfg
  14. 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.