Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / ae32b95fdb265ecf1c9a94a652b60f47fc931f66
commitae32b95fdb265ecf1c9a94a652b60f47fc931f66[log] [tgz]
authorXin Li <delphij@google.com>Thu Oct 05 15:42:44 2023 -0700
committerXin Li <delphij@google.com>Thu Oct 05 15:42:44 2023 -0700
tree53b71ce78af957a07cd00414864badc5daf74996
parent25a6a5df1bd467c70ef7b625343a48eeec557265 [diff]
parentdd34bb23fa60c7d438ccd3d144771a3ff9dbdec0 [diff]
Merge Android 14

Bug: 298295554
Merged-In: I8af5d3dd8733d244c2ade1d9b5118308b3c00622
Change-Id: I8013f4106601f2f87816344edb6ff8fe489449b9
tree: 53b71ce78af957a07cd00414864badc5daf74996
  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.