Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 356902a4e7a3f5685775ebe1f0a89882f9eeb54a
commit356902a4e7a3f5685775ebe1f0a89882f9eeb54a[log] [tgz]
authorPaul Duffin <paulduffin@google.com>Fri Mar 25 12:13:14 2022 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Fri Mar 25 12:13:14 2022 +0000
treebbf097efdd29eadd2f74d14cd693974390815770
parenta0bb464604599f0fea711219f0130c7bfea1e818 [diff]
parent633237ddd98f5f9e3c5e97c4cff648e6313015c3 [diff]
Fix failures caused by lack of ANDROID_BUILD_TOP on build servers am: aad984bea1 am: be5c0a1434 am: 633237ddd9

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

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