Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 8b87eacbff4259059bf040b9e47400b6d4f8f41f
commit8b87eacbff4259059bf040b9e47400b6d4f8f41f[log] [tgz]
authorRemi NGUYEN VAN <reminv@google.com>Thu Apr 06 13:19:51 2023 +0900
committerRemi NGUYEN VAN <reminv@google.com>Thu Apr 06 13:22:27 2023 +0900
tree4d43f7b2a414609c866d00c6134986d92b9e8fc0
parent8bcf9b4f35c919b4cd076ef4ea7a9b80bef88124 [diff]
Add current/next libs to allowed_deps

While they are not actually going to be shipped in updates, this allows
the Next targets to use the same standard setup and simplifies
maintenance.

Apex-Size-Increase: None
Previous-Platform-Support: Yes
Aosp-First: Yes
Test-Info: Part of NetworkStack tests
Test: m

Change-Id: Ib07db5de953cf075edb298a9e0abbf9cae46d4e0
1 file changed
tree: 4d43f7b2a414609c866d00c6134986d92b9e8fc0
  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.