Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 664b18304e67edc3cf7cf696e35e9dacb4eb0e20
commit664b18304e67edc3cf7cf696e35e9dacb4eb0e20[log] [tgz]
authorAnvesh Renikindi <renikindi@google.com>Tue Jun 11 05:26:27 2024 +0000
committerAnvesh Renikindi <renikindi@google.com>Wed Jun 12 16:19:15 2024 +0000
tree402c1ebe8f7ee6becf55b0aac4f8b16a674e460a
parentacdeb4f1b74884e55ee8b8f08fc1bd538690fa9c [diff]
min sdk bump from 19 to 21

Change-Id: I0e7ac5222d853dd296c589f907a095ed5e66d9c8
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: 402c1ebe8f7ee6becf55b0aac4f8b16a674e460a
  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.