Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 26f3e59bafd4701c00b5679517dfab9d80f4a49e
commit26f3e59bafd4701c00b5679517dfab9d80f4a49e[log] [tgz]
authorSorin Basca <sorinbasca@google.com>Wed Jun 12 17:14:47 2024 +0100
committerSorin Basca <sorinbasca@google.com>Wed Jun 12 17:15:33 2024 +0100
treebcb706c9161f6b7bca82749cd3e6d48d6e4b6f1d
parent61ae1b30ef81f315e798c4275bd69b1368172c64 [diff]
Upgrade ASM to 9.6

Bug: 342332820
Test: RUN_ERROR_PRONE=true m -j96 javac-check lint-check dist
Test: Forrest build.
No-Allowed-Deps-Check: Only affects coverage builds.
Change-Id: Ibff5f723afe49304940d98d03e539c4f51237dd8
1 file changed
tree: bcb706c9161f6b7bca82749cd3e6d48d6e4b6f1d
  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.