Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 293800240aa9e2409a27da81561b9a20b619aab1
commit293800240aa9e2409a27da81561b9a20b619aab1[log] [tgz]
authorAnton Hansson <hansson@google.com>Thu Apr 07 12:50:38 2022 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Thu Apr 07 12:50:38 2022 +0000
treebf87a86952b80c0bf43feff293f122b6b6bd0422
parenta0077034720d4b1aff4a7f6461ebbb5c85d4ad71 [diff]
parent4d526da8b26c616aead2852a9d0d461fd38b3ff6 [diff]
Merge changes I31848ad3,Icaf4937b,Ie7b44da3,I94f7c6f0 am: f949851fc0 am: 4d526da8b2

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

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