Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / dac2c2c438e17eb243a9aff803c46669ad52587a
commitdac2c2c438e17eb243a9aff803c46669ad52587a[log] [tgz]
authorTreehugger Robot <treehugger-gerrit@google.com>Fri Jan 06 22:19:03 2023 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Fri Jan 06 22:19:03 2023 +0000
tree99054c0e0e9496516435c8db01055b109d95d999
parente071b5b62e6f7d56597630558700b150e4bc605d [diff]
parent5b73818073cc5309955526f8fad4902c8101d615 [diff]
Merge "Add libui dependencies" am: 5b73818073

Original change: https://android-review.googlesource.com/c/platform/packages/modules/common/+/2377408

Change-Id: I24c63e102c5829ae3c165615cf2b217235384560
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: 99054c0e0e9496516435c8db01055b109d95d999
  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.