Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 2cb57155b140b05a78e6ccfebba498782eaec610
commit2cb57155b140b05a78e6ccfebba498782eaec610[log] [tgz]
authorAnvesh Renikindi <renikindi@google.com>Wed May 01 20:49:23 2024 +0000
committerAnvesh Renikindi <renikindi@google.com>Wed May 29 13:55:04 2024 +0000
tree3bb3cbf31e2d8fa3ba2c8d0d4c1d84f915170f3a
parentb46307a32e2637dbdc4ed406667fc759c02b8850 [diff]
Updated minsdkversion 19 to 21

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