Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 4ccc7837cbb503ba552e105b0be485d7d67468fd
commit4ccc7837cbb503ba552e105b0be485d7d67468fd[log] [tgz]
authorHassan Ali <hsnali@google.com>Wed Jun 22 13:35:29 2022 +0000
committerCherrypicker Worker <android-build-cherrypicker-worker@google.com>Thu Jun 23 13:20:41 2022 +0000
treeb019e85128226ee546edcce795d44aa821bbfe94
parent637c7ce91ba8226f48b00d3b40579e820c915885 [diff]
Set libmodules utils build min sdk version to 29

Test-Info: No behavior change.
Aosp-First: yes
Previous-Platform-Support: 29
Apex-Size-Increase: 0

Ignore-AOSP-First: Cherry-pick on AOSP will follow
Bug: 175670047
Test: m
Change-Id: I788f4287df2130750b32b9e07d73043ed1433c98
(cherry picked from commit a922e3d9a3681404e9adf7dac2e94fac6a2c6a77)
Merged-In: I788f4287df2130750b32b9e07d73043ed1433c98
1 file changed
tree: b019e85128226ee546edcce795d44aa821bbfe94
  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.