DO NOT MERGE Add sdk modules list in build artifacts root.

Add list of all the sdk supported modules in sdk-modules.txt. This file
should generate for all builds (even when only non-sdk modules build is
requested).
The file only contains modules which are requested by the build, and
supports sdk.

Bug: 242316893

Test: Generate sdk-modules.txt in the dist directory root.
Test: atest --host mainline_modules_sdks_test --no-bazel-mode
(cherry picked from https://android-review.googlesource.com/q/commit:d822398d79d5fa8def8ead2759624d8b99c06e1f)
Merged-In: Ic8aa3c63209717e1076c4c51f1232dd5afcdd6d4
Change-Id: Ic8aa3c63209717e1076c4c51f1232dd5afcdd6d4
2 files changed
tree: ac97ae9fa344e1a713a690bc2c4d1dd6be03dbaa
  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.