Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 06b08a1c59edd52cd85d23bed31f5a156afac39a
commit06b08a1c59edd52cd85d23bed31f5a156afac39a[log] [tgz]
authorPatrick Rohr <prohr@google.com>Tue Jan 24 16:32:22 2023 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Tue Jan 24 16:32:22 2023 +0000
tree59f887b4badb603388ba2c42a4807877734276cb
parent4e89f0ffc3fb92e2b82ecc88505ef9c2308dbde3 [diff]
parent921de9667362fadcb679beaebb2584905b667cd3 [diff]
cronet: remove framework-cronet.xml from allowed deps am: 921de96673

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

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