Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 07171bd950f96f0be96126dbe0910d9815c785c4
commit07171bd950f96f0be96126dbe0910d9815c785c4[log] [tgz]
authorKrzysztof Kosiński <krzysio@google.com>Tue Apr 25 09:51:08 2023 +0000
committerKrzysztof Kosiński <krzysio@google.com>Thu Apr 27 01:28:30 2023 +0000
treee12f5a85df94c373911cbc877a8b9d4e7cb2f449
parentaec473404b7ad73facf5507bbadbd3fdece732eb [diff]
Add gRPC 1.17.1 libraries to the list.

No-Allowed-Deps-Check: The new deps are simply new private static
libraries in an existing dependency, not a new dependency.

Bug: 279548314
Test: presubmit
Change-Id: I14c3fd62ec6ab70df3f43520355c400502c179b5
1 file changed
tree: e12f5a85df94c373911cbc877a8b9d4e7cb2f449
  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.