Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 892a0235068fd10946efb6e02e23f93e2af6cb91
commit892a0235068fd10946efb6e02e23f93e2af6cb91[log] [tgz]
authorJooyung Han <jooyung@google.com>Mon Jun 27 19:12:00 2022 +0900
committerJooyung Han <jooyung@google.com>Wed Jun 29 06:41:58 2022 +0900
tree3a4a8213be0753699e0fb925091c3793cc3bbe6c
parent585db4003eb418f02ac746931e8a5b0f9ca9c4f2 [diff]
Remove min_sdk_version allowlist

Ignore-AOSP-First: avoid merge conflicts

Bug: 158059172
Test: m
Merged-In: I65ca75ae2cce263e76f099951261e6e219a585cf
Change-Id: I65ca75ae2cce263e76f099951261e6e219a585cf
(cherry picked from commit 06e3d18d5e5141f155f4ccc03ac0b70fb5aaf2f0)
1 file changed
tree: 3a4a8213be0753699e0fb925091c3793cc3bbe6c
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. MODULES_OWNERS
  9. OWNERS
  10. PREBUILTS_MODULE_OWNERS
  11. PREUPLOAD.cfg
  12. 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.