Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / cd582f705727596663371319c95f5123f96be160
commitcd582f705727596663371319c95f5123f96be160[log] [tgz]
authorXin Li <delphij@google.com>Fri Apr 01 20:32:52 2022 +0000
committerXin Li <delphij@google.com>Fri Apr 01 20:32:52 2022 +0000
treea6522b8439ebe919fe24ed32f2bf4940fcf9d0cc
parent677f1c43b85cee42005ccc509ba044f54d3b2163 [diff]
parent77dbb91235ed1f54b4252a64fb39314af19614c4 [diff]
Merge Android 12 QPR3 ab/8391262

Bug: 226662282
Merged-In: I737f29e2eec4465be532b57d51f2c31c2ebab842
Change-Id: I97c4306945a6269dd635a5efae7ae09f66ba2631
tree: a6522b8439ebe919fe24ed32f2bf4940fcf9d0cc
  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.