Google Git
Sign in
android / platform / packages / modules / common / refs/tags/platform-tools-33.0.0
tag40673bb37e2e9204243c547c954e66d97fbdb55f
taggerThe Android Open Source Project <initial-contribution@android.com>Thu May 19 16:15:31 2022 -0700
object82bd33f860986872d2e8e03e31086538ac9f87fd 
Platform Tools Release 33.0.0 (8141338)
commit82bd33f860986872d2e8e03e31086538ac9f87fd[log] [tgz]
authorAndroid Build Coastguard Worker <android-build-coastguard-worker@google.com>Wed Feb 02 09:22:12 2022 +0000
committerAndroid Build Coastguard Worker <android-build-coastguard-worker@google.com>Wed Feb 02 09:22:12 2022 +0000
treef55a81888ea8387670220f28b3079cd079b153a5
parentff680ddea986467266eedd7455313ce7643ccead [diff]
parent1abdf7a0fb9832019282ab0546a43d2230ea5c49 [diff]
Snap for 8140651 from 1abdf7a0fb9832019282ab0546a43d2230ea5c49 to sdk-release

Change-Id: I2774395aee7269f33c83fe8906a5c9590b6181bb
tree: f55a81888ea8387670220f28b3079cd079b153a5
  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.