Google Git
Sign in
android/platform/packages/modules/common/refs/heads/build-tools-release
commit
b664baf347bf51c2821590dea97bd59a56f63a75
[log]
author
Android Build Coastguard Worker <android-build-coastguard-worker@google.com>
Fri Mar 14 10:26:59 2025 -0700
committer
Android Build Coastguard Worker <android-build-coastguard-worker@google.com>
Fri Mar 14 10:26:59 2025 -0700
tree
2984756a9df55771911b2c222d1248acffcd9928
parent
80b1a2f26c7c679a3141c0d071e1b51b16d69204 [diff]
parent
b4899a3720fb8beb622a2486fe69e6ab3c9591b3 [diff]
Snap for 13217294 from b4899a3720fb8beb622a2486fe69e6ab3c9591b3 to build-tools-release

Change-Id: I4cadab01c3bcb852561e19e9e22189f6928a3c4d
tree: 2984756a9df55771911b2c222d1248acffcd9928
  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.