Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 9027e36fa376499d072621e01ac79e8251645e48
commit9027e36fa376499d072621e01ac79e8251645e48[log] [tgz]
authorAnvesh Renikindi <renikindi@google.com>Thu May 30 04:19:35 2024 +0000
committerAnvesh Renikindi <renikindi@google.com>Thu May 30 04:19:41 2024 +0000
treea870278aac5a9252614b5f1ee6bffec71ca5e417
parent639ae3838998c242717c8579d23104e3674b4ab3 [diff]
emoji2 minsdk bump from 19 to 21


Change-Id: I9730832c1c3358459c59441e891c255219fb21f7
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: a870278aac5a9252614b5f1ee6bffec71ca5e417
  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.