Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 300ec921e581f9ca0fdba0499897d71f8337cc0f
commit300ec921e581f9ca0fdba0499897d71f8337cc0f[log] [tgz]
authorPaul Duffin <paulduffin@google.com>Fri Jan 21 18:43:39 2022 +0000
committerPaul Duffin <paulduffin@google.com>Fri Jan 21 19:36:46 2022 +0000
treebe5c96d341d652389dabc4f3f52c48ea3e3f2d76
parent661845d4ec2247abab8618e6c7d6368f1b077cb5 [diff]
Move MAINLINE_MODULE_BY_APEX into the test file

The variable is only used by the tests.

Test: atest mainline_modules_sdks_test
      packages/modules/common/build/mainline_modules_sdks.sh
      tree out/dist/mainline-sdks out/dist/stubs
      - check that it is identical to before this change
Bug: 204763318
Change-Id: I38c4ce218825d79de831868af814c43ce8a6d60f
2 files changed
tree: be5c96d341d652389dabc4f3f52c48ea3e3f2d76
  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.