Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / a9df5457ad322e953c1d4560abafd3cd9dd94b35
commita9df5457ad322e953c1d4560abafd3cd9dd94b35[log] [tgz]
authorJingwen Chen <jingwen@google.com>Mon Mar 20 19:25:57 2023 +0000
committerLiz Kammer <eakammer@google.com>Mon Mar 20 20:24:14 2023 +0000
tree76b233e5ac0233af383d9f84b1893e13d318dd71
parenta35f7b99f3611a8395e3eb0cacb39d06a2e90efd [diff]
parentbbc57ef1c6ae69e668752e7d27e93f702712c436 [diff]
[conflict] Enable bazel in mainline build script. am: be577742a1 am: d8af540729 am: bbc57ef1c6

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

Bug: 263406837
Ignore-AOSP-First: merge conflict resolution.
Change-Id: Ie80461852c504eec276b80459955596f7ffc128a
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: 76b233e5ac0233af383d9f84b1893e13d318dd71
  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.