Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 261025ee07bb637ce53453b57b1982f36a675499
commit261025ee07bb637ce53453b57b1982f36a675499[log] [tgz]
authorAlex Buynytskyy <alexbuy@google.com>Mon Jan 23 12:37:30 2023 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Mon Jan 23 12:37:30 2023 +0000
tree79128ae05d27b45866fd060b720e052b1da9531f
parent8740733a2a7233692bc835633036eaec45572ce9 [diff]
parent100994c4c7de15531f57f204d22ffdd55772efab [diff]
Addressing CL comments. am: 354a18b679 am: 100994c4c7

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

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