Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 9a4153dad8eeaa237d85a04d95d9b74fcce68ce7
commit9a4153dad8eeaa237d85a04d95d9b74fcce68ce7[log] [tgz]
authorAnvesh Renikindi <renikindi@google.com>Mon Apr 08 16:43:25 2024 +0000
committerAnvesh Renikindi <renikindi@google.com>Mon Apr 08 20:28:23 2024 +0000
treeab8192d986c218a94270698480d7e37aca45ba8c
parenta5969520d1ee99df045107ce46af1c734690102a [diff]
Update tracing_tracing-ktx and tracing_tracing-ktx-nodeps

Aosp-First: No
Change-Id: Ia5d77ca35dfb9d5a9f17d46c4fb086b586cdacbd
Merged-In: Ia5d77ca35dfb9d5a9f17d46c4fb086b586cdacbd
Apex-Size-Increase:
Previous-Platform-Support: yes
Test-Info:Android JUnit Test
ignore-AOSP-First: Merge conflict resolution
Test: NA
1 file changed
tree: ab8192d986c218a94270698480d7e37aca45ba8c
  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.