Google Git
Sign in
android/platform/packages/modules/common/refs/heads/android13-d2-release
commit
b3080c3c1552c3e6d1def9544ee0a8b6da305bf8
[log]
author
Android Build Coastguard Worker <android-build-coastguard-worker@google.com>
Fri Jan 20 00:25:52 2023 +0000
committer
Android Build Coastguard Worker <android-build-coastguard-worker@google.com>
Fri Jan 20 00:25:52 2023 +0000
tree
b1d788843de8791b66763a8643e486df37520cc8
parent
19402cb68ab5a2cca2a0434ad8c2ed6bb0e87227 [diff]
parent
3360760531e042d83b82643769af8dc2e464fe8e [diff]
Snap for 9509315 from 3360760531e042d83b82643769af8dc2e464fe8e to tm-d2-release

Change-Id: Ib2793457f1ef0d49cb38a60f0f26d5644340c5b2
tree: b1d788843de8791b66763a8643e486df37520cc8
  1. build/
  2. java/
  3. javatests/
  4. proguard/
  5. proto/
  6. sdk/
  7. tools/
  8. Android.bp
  9. generate_ml_bundle.sh
  10. MODULES_OWNERS
  11. OWNERS
  12. PREBUILTS_MODULE_OWNERS
  13. PREUPLOAD.cfg
  14. 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.