Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 8a45abd07da9c30ab083c4e4e1a1378ece559727
commit8a45abd07da9c30ab083c4e4e1a1378ece559727[log] [tgz]
authorAnvesh Renikindi <renikindi@google.com>Mon Jun 03 12:40:08 2024 +0000
committerAnvesh Renikindi <renikindi@google.com>Mon Jun 03 12:40:15 2024 +0000
treeb3b4244100fdd41ae53b474fefd96027246a7ac4
parentdd0bd38c61f394834e7896da38c060b781f3b72d [diff]
Updating min sdk bump from 19 to 21

Change-Id: Iccb48396e5c35f2c8dcfd86a82f6bca0217da4a5
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: b3b4244100fdd41ae53b474fefd96027246a7ac4
  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.