Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 7b521b7fcab598cc12ad5b945152e9fd18a7c639
commit7b521b7fcab598cc12ad5b945152e9fd18a7c639[log] [tgz]
authorPaul Duffin <paulduffin@google.com>Tue Mar 28 12:36:20 2023 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Tue Mar 28 12:36:20 2023 +0000
tree10503e7661e9a5a645395e6f348b2f39ad4f426e
parentc2829a31bf753d3cdd725929a16cd85cbcb4f1d1 [diff]
parentd406af5bdae4b5e244b9ab595e89bad48294cd47 [diff]
Revert "Pass BuildRelease to apply and _apply_transformation methods" am: d406af5bda

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

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