Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 50e2a0a4068e1ea962aa2857c0b05027b29167c3
commit50e2a0a4068e1ea962aa2857c0b05027b29167c3[log] [tgz]
authorCharles Chen <charlesccchen@google.com>Thu Apr 25 19:00:59 2024 +0800
committerCharles Chen <charlesccchen@google.com>Tue Apr 30 11:50:54 2024 +0800
tree60aa0d4b28d2317aa090410fd67c44efbe3644c3
parent692fd71a173a5ef79cf4df56788bc125256a40fa [diff]
Update dependency

Update dependency due to Jetpack library update.
Apex-Size-Increase: 33.7KB
Previous-Platform-Support: 19
Aosp-First: No
Ignore-AOSP-First: changes in topics with internal-first/internal-only projects
Test-Info: presubmit
Bug: 322508920
Bug: 329997430
Test: presubmit

Change-Id: Ib2d6097eaed4c77fc5a3aea9c2986cfdb7dfb08b
1 file changed
tree: 60aa0d4b28d2317aa090410fd67c44efbe3644c3
  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.