Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 94b1430ffe9fd49a2439e2c20fac0f6a9fd8364c
commit94b1430ffe9fd49a2439e2c20fac0f6a9fd8364c[log] [tgz]
authorsatayev <satayev@google.com>Tue Nov 09 14:41:18 2021 +0000
committersatayev <satayev@google.com>Tue Nov 09 14:41:18 2021 +0000
treeb481fe34e4149a1bef2b960d5d7d795e6c6be248
parent5d9396e2ba81b5a75583217efc86d88577d9d7c5 [diff]
Change min max sdk version type to string.

This allows support of codenames, instead of pure integer version codes.

This is a safe change, since the fields are currently unused.

Bug: 190818041
Test: presubmit
Change-Id: Ic80330413c35f16d274fef721ff908f1fe380e55
1 file changed
tree: b481fe34e4149a1bef2b960d5d7d795e6c6be248
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. generate_ml_bundle.sh
  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.