Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 93cbe96cc63ae43f84a993d48724233197bb615f
commit93cbe96cc63ae43f84a993d48724233197bb615f[log] [tgz]
authorAnvesh Renikindi <renikindi@google.com>Wed Jun 12 20:27:27 2024 +0000
committerAnvesh Renikindi <renikindi@google.com>Thu Jun 13 02:13:37 2024 +0000
treeadecfbf3e9184f78dbddb4d2985aa293aee8f7ff
parent664b18304e67edc3cf7cf696e35e9dacb4eb0e20 [diff]
minsdk bump update from 19 to 21

Change-Id: I10a68369d1a1c405e66aebdd3e044b6800822859
Aosp-First: No
Apex-Size-Increase:
Previous-Platform-Support: yes
Test-Info:Android JUnit Test
ignore-AOSP-First: Merge conflict resolution
Bug:340711546
1 file changed
tree: adecfbf3e9184f78dbddb4d2985aa293aee8f7ff
  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.