Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 2b134da2e92080e1d7657bb182bca6f89ffdc6f6
commit2b134da2e92080e1d7657bb182bca6f89ffdc6f6[log] [tgz]
authorAnvesh Renikindi <renikindi@google.com>Mon Apr 29 22:17:07 2024 +0000
committerAnvesh Renikindi <renikindi@google.com>Thu May 30 02:59:25 2024 +0000
tree8acac25ee420b51495e1cc5a49e0b6abfddbed0d
parent639ae3838998c242717c8579d23104e3674b4ab3 [diff]
Bumping minsdkversion to 21

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