Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 45f7051eff48ab099af579610f62ff1e7260d75c
commit45f7051eff48ab099af579610f62ff1e7260d75c[log] [tgz]
authorPaul Duffin <paulduffin@google.com>Wed Mar 23 10:07:37 2022 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Wed Mar 23 10:07:37 2022 +0000
tree6f67023921ba7b6d57e1c0820da80b08f9189306
parent5c78b6d3d6cbf7e149cd81e9773c8590873eddc9 [diff]
parent6e6569d1ab0d1eb8240e760b5860f91083e15d82 [diff]
Merge "Decouple population of the dist dir from the SnapshotBuilder" am: 726f9ab1bf am: 6e6569d1ab

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

Change-Id: Iedcf4cb032dcaa398df49577fc3bacaed7446ba7
tree: 6f67023921ba7b6d57e1c0820da80b08f9189306
  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.