Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 56f66a8f17af5b58a9e48d572f5c010157d70c04
commit56f66a8f17af5b58a9e48d572f5c010157d70c04[log] [tgz]
authorHassan Ali <hsnali@google.com>Wed Jun 22 12:41:57 2022 +0000
committerHassan Ali <hsnali@google.com>Thu Jun 23 14:42:16 2022 +0000
tree02b0a29a90f7e65ca0a03c05857f0c02b804f647
parentf874f0bca973f55df361ce415e57cf915f6511cf [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

Bug: 175670047
Test: m
Change-Id: I788f4287df2130750b32b9e07d73043ed1433c98
Merged-In: I788f4287df2130750b32b9e07d73043ed1433c98
1 file changed
tree: 02b0a29a90f7e65ca0a03c05857f0c02b804f647
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. MODULES_OWNERS
  9. OWNERS
  10. PREBUILTS_MODULE_OWNERS
  11. PREUPLOAD.cfg
  12. 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.