Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / f9a957a5c62cabafd3891fcd17955a1e206b8a87
commitf9a957a5c62cabafd3891fcd17955a1e206b8a87[log] [tgz]
authorPaul Duffin <paulduffin@google.com>Wed Mar 30 18:06:15 2022 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Wed Mar 30 18:06:15 2022 +0000
tree210e182afc7e86592e4c396435fde26216cb6844
parentfdaf5d0d1c1192f97b69b63ef8d498143614e906 [diff]
parent131657caf4b3b87bb1c00e136f9a38328fc62dc1 [diff]
mainline_modules_sdks.py: Optimize snapshot build order am: b3805c1d35 am: 131657caf4

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

Change-Id: I89f340c6499c1a15e6e30e6b32470815597d8bc0
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: 210e182afc7e86592e4c396435fde26216cb6844
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. generate_ml_bundle.sh
  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.