Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / db747e124dafe1ff051bff2b483e625874523a4b
commitdb747e124dafe1ff051bff2b483e625874523a4b[log] [tgz]
authorAnvesh Renikindi <renikindi@google.com>Thu May 30 03:48:53 2024 +0000
committerAnvesh Renikindi <renikindi@google.com>Thu May 30 03:49:00 2024 +0000
tree65eceeeb8c424359c5506b1d01c982315233cbc6
parent639ae3838998c242717c8579d23104e3674b4ab3 [diff]
Update minsdk bump from 19 to 21

Change-Id: Iedc92a3f585dd8f1e63423b9023d52672d57af39
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: 65eceeeb8c424359c5506b1d01c982315233cbc6
  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.