Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / c3c8c175b91bc3f1840d3ac935e96775d28d0651
commitc3c8c175b91bc3f1840d3ac935e96775d28d0651[log] [tgz]
authorLorenzo Colitti <lorenzo@google.com>Fri Apr 01 22:15:06 2022 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Fri Apr 01 22:15:06 2022 +0000
tree717ea403346e04e7ffae6e40497dcf2fb08f67e7
parent677f1c43b85cee42005ccc509ba044f54d3b2163 [diff]
parent27af85827a3e42537dcac9a4854196c6b371584c [diff]
Merge "Update deps for ConnectivityNative" am: 27af85827a

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

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