Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 83db20efa4bd6eb63529b259c9f45da9168bae15
commit83db20efa4bd6eb63529b259c9f45da9168bae15[log] [tgz]
authorRam Mohan <ram.mohan@ittiam.com>Wed Jul 12 22:00:06 2023 +0530
committerMikhail Naganov <mnaganov@google.com>Tue Aug 01 17:45:24 2023 +0000
tree82c82bab8582e2dc79ac3d8cb4b7491ee3d28048
parenteabef208a7447903e9220ccc135c9185921f9403 [diff]
update allowed_deps.txt with aidl hardware common interface

Bug: 228804498
Test: m
Apex-Size-Increase: no change in libbluetooth_jni.so
Previous-Platform-Support: yes
Aosp-First: yes
Test-Info: m

Change-Id: I601d9ee5a5630db497673d3f0b3ad543920d0b47
Merged-In: I601d9ee5a5630db497673d3f0b3ad543920d0b47
1 file changed
tree: 82c82bab8582e2dc79ac3d8cb4b7491ee3d28048
  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.