Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 1d8ad95c92be5b4bfc8700d337d1581e7aa22c48
commit1d8ad95c92be5b4bfc8700d337d1581e7aa22c48[log] [tgz]
authorAnvesh Renikindi <renikindi@google.com>Fri Mar 31 23:54:44 2023 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Fri Mar 31 23:54:44 2023 +0000
tree37d0a1b6a104270ba77066c1e63af41fa039cbcb
parent2fc659a45931f345eacda76a726cf2603f3b08b7 [diff]
parenta45a8d27a73430624c5dda25fd5fc76a124d9258 [diff]
Added deps am: a45a8d27a7

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

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