Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / d2e3e30c70d1bc48f07dbbfd51329e7f3619569a
commitd2e3e30c70d1bc48f07dbbfd51329e7f3619569a[log] [tgz]
authorXin Li <delphij@google.com>Thu Jan 12 13:27:13 2023 -0800
committerThe Android Open Source Project <initial-contribution@android.com>Thu Jan 12 16:10:13 2023 -0800
treea96281ec2b91b7036d52a900e080071cf01be5ac
parent2fc9185748e3aec51bd09aa206d451981731ad93 [diff]
parenta37b0eac59a1a3484ab3c026a6131c7a8e9cac51 [diff]
Merge AOSP trunk

Bug: 262638121
Merged-In: I4127e843cf1caf460a1c6b949a97ef3418ff895c
Change-Id: Ic6c35a46bb462f904e8e2802853715cc57c92729
tree: a96281ec2b91b7036d52a900e080071cf01be5ac
  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.