Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 7c3ab894437a6e12eacb657a9964968446672f19
commit7c3ab894437a6e12eacb657a9964968446672f19[log] [tgz]
authorZhi Dou <zhidou@google.com>Fri Mar 17 16:20:59 2023 +0000
committerzhidou <zhidou@google.com>Fri Mar 24 16:20:42 2023 +0000
tree10503e7661e9a5a645395e6f348b2f39ad4f426e
parentb50e8ce2fbc2770c5c155a490d1b81e02d579f21 [diff]
Adding additional_transformations

Add additional_transformations for module sdk build. This feature is
only supported by S+ releases.

Bug: 254111089
Test: atest mainline_modules_sdks_test --host
Ignore-AOSP-First: Check into internal branch first to make sure all
testing works.

Merged-In: I94989519011e31c7db33656c6730c4f8fd5e0a4f
Change-Id: Idc8bd682550f59e086c431b0be38bfbdf8a75127
3 files changed
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.