Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 5794d99ee661408f9cbadea723e2eae6ffda428e
commit5794d99ee661408f9cbadea723e2eae6ffda428e[log] [tgz]
authorJane Ha <hatrang@google.com>Wed Apr 19 22:23:24 2023 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Wed Apr 19 22:23:24 2023 +0000
tree28d1793e04a782f281621f2996d3cb8fdca2ee4b
parent49494e694030d4b92cd006881553cddcab999912 [diff]
parent85c55349df3fca87b97a807cbc33d0833c70aadc [diff]
[automerge] Ignore-AOSP-First: merge conflict. see aosp/2545210 2p: 478c28bbc8 am: 85c55349df

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

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