Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 83039153c9f75aced05173017b21863b4164f93e
commit83039153c9f75aced05173017b21863b4164f93e[log] [tgz]
authorPaul Duffin <paulduffin@google.com>Thu Mar 24 17:17:44 2022 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Thu Mar 24 17:17:44 2022 +0000
treecccd8330d48700f400998fa4ff546ba3fa722e8b
parent85771027a8caa0b2d099a2c3028bf1ce04c64c8f [diff]
parentdaf654e980e3489b303902d216b67535e30eedcc [diff]
Generate sdk snapshots for the R build am: ffa89fd0a0 am: fdd3e454dc am: daf654e980

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

Change-Id: I038e1735e3c1ed61a6e8cee3c125a3144d40e6cd
tree: cccd8330d48700f400998fa4ff546ba3fa722e8b
  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.