Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / c27a472e77727cced1423e9ebd482e9f6f12037e
commitc27a472e77727cced1423e9ebd482e9f6f12037e[log] [tgz]
authorAndrew Walbran <qwandor@google.com>Wed Sep 11 14:48:17 2024 +0100
committerAndrew Walbran <qwandor@google.com>Wed Sep 11 14:48:17 2024 +0100
tree400376a5ec531844a3f3bf177dfe706dbe5d4a57
parent33cc5acc6fc6c5b28637f5fe7c1ee413acbb0794 [diff]
min_sdk_version of tempfile increased.

Bug: 313489216
Test: TreeHugger
Apex-Size-Increase: Depends on the APEX, should be statically linked
Previous-Platform-Support: no
Aosp-First: external
Test-Info: external
Change-Id: I163a2184f434f4b93eef3ac4ccfe06a380a03e2b
1 file changed
tree: 400376a5ec531844a3f3bf177dfe706dbe5d4a57
  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.