Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 8b70c5ed2f2371a5361ff1c3df9eacbb290140ee
commit8b70c5ed2f2371a5361ff1c3df9eacbb290140ee[log] [tgz]
authorPriyanka Advani (xWF) <padvani@google.com>Mon Sep 23 22:46:39 2024 +0000
committerAndroid (Google) Code Review <android-gerrit@google.com>Mon Sep 23 22:46:43 2024 +0000
tree927661e80b918028bd3d696bdcd2fa9c3bbd1328
parente002073b0f12bf8c460c698d272b6c50533815bc [diff]
Revert "add new dependency"

Revert submission 29548404-add_new_lib_1

Reason for revert: Droidmonitor created revert due to b/369212221.

Reverted changes: /q/submissionid:29548404-add_new_lib_1

Change-Id: I42de0c9751d780a0a34e7e646d87a483d8e09aec
1 file changed
tree: 927661e80b918028bd3d696bdcd2fa9c3bbd1328
  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.