Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / b50e8ce2fbc2770c5c155a490d1b81e02d579f21
commitb50e8ce2fbc2770c5c155a490d1b81e02d579f21[log] [tgz]
authorZhi Dou <zhidou@google.com>Wed Mar 22 20:30:42 2023 +0000
committerzhidou <zhidou@google.com>Fri Mar 24 16:15:44 2023 +0000
tree17a6765c8febe56b221066ad2f3dae58add49cfc
parent653f88116179584d7dfa8ade6ce7e0851ef41e1a [diff]
Pass BuildRelease to apply and _apply_transformation methods

Pass BuildRelease to apply and _apply_transformation methods in class of
transformations, so that transformation could use the build_release
information to decide whether certain steps of the transformation should
be performed.

Test: atest mainline_modules_sdks_test --host
Bug: 254111089
Merged-In: If71a921752f4c481030efb0fd391fb328b5dffb6

Change-Id: I8341541572072ef72ab37dfe816296a1375e4cea
2 files changed
tree: 17a6765c8febe56b221066ad2f3dae58add49cfc
  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.