Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / ab45d2e606c1424f710cfdf1546303aa7915717a
commitab45d2e606c1424f710cfdf1546303aa7915717a[log] [tgz]
authorVikram Gaur <vikramgaur@google.com>Fri Dec 09 21:15:18 2022 +0000
committerAnton Hansson <hansson@google.com>Wed Dec 14 17:48:45 2022 +0000
tree6659356c574d087051902fac5585466bd6265bfd
parent29a7bfb44952ca50a700c0068696517d06f8a614 [diff]
Add RemoteKeyProvisioning in mainline_modules_sdks.py

Test: Build
Change-Id: Ifb5284a9a0057611aaee32a28273f9583c3cad42
Merged-In: Ifb5284a9a0057611aaee32a28273f9583c3cad42
Merged-In: Ie3a4f694dabee4224444b1aa6da0a0048b69fc75
1 file changed
tree: 6659356c574d087051902fac5585466bd6265bfd
  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.