Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 50960ceaab0a874c9078d9e55b1fc38edd7bed9d
commit50960ceaab0a874c9078d9e55b1fc38edd7bed9d[log] [tgz]
authorAnvesh Renikindi <renikindi@google.com>Thu Feb 23 19:23:35 2023 +0000
committerAnvesh Renikindi <renikindi@google.com>Wed Mar 15 02:37:34 2023 +0000
tree94c6524bcb6b6e46a37a74d3185e26c0f143adcd
parent6d5a205089030d7f7b595d88296b7a43114fb568 [diff]
Added Deps


Change-Id: Ia0e97abb97fb5b4167736e23392ef7f6fcce24d9
Merged-In: Ia0e97abb97fb5b4167736e23392ef7f6fcce24d9
Test: None
Aosp-First: No(Internal submitted)
Apex-Size-Increase:47.6 kb
Previous-Platform-Support:yes
Test-Info: Android JUnit Test
1 file changed
tree: 94c6524bcb6b6e46a37a74d3185e26c0f143adcd
  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.