Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 211a4e2b51bb75d0e744ee73729ba297ede7829c
commit211a4e2b51bb75d0e744ee73729ba297ede7829c[log] [tgz]
authorAnton Hansson <hansson@google.com>Thu May 12 11:42:06 2022 +0000
committerAnton Hansson <hansson@google.com>Thu May 12 11:42:06 2022 +0000
tree491c03b7f209d65e41579adf434d2a98af2d7507
parent7d96e47a39eb4cc578b50fd71c38b2651ff47ad5 [diff]
Update path to module SDKs

The "current" directory is going to be removed.

Test: No
Change-Id: I69669cfba5514ccb590e441537ae0377fb3cdf71
1 file changed
tree: 491c03b7f209d65e41579adf434d2a98af2d7507
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. generate_ml_bundle.sh
  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.