Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 0fcc36bd4981f8a9336acc5ce424eeaac0661d2d
commit0fcc36bd4981f8a9336acc5ce424eeaac0661d2d[log] [tgz]
authorSaeid Farivar Asanjan <farivar@google.com>Tue Apr 18 19:10:02 2023 +0000
committerSaeid Farivar Asanjan <farivar@google.com>Sun Apr 23 19:27:49 2023 +0000
tree1ad3c959ac4d18d96545ce68748ab0d42686cbd0
parent34496beebc9a1ed2b1463df10e888bd1de1ec6e4 [diff]
Ignore-AOSP-First: Add new rotary targets to apex allowlist

adding the following targets to apex allowlist
car-rotary-lib-no-overlayable
car-rotary-lib-overlayable-resources

Test-Info: atest CarUILibUnitTest
Previous-Platform-Support: Yes
Aosp-First: Yes
Apex-Size-Increase: No

Bug: 266871187
Test: m car-rotary-lib-no-overlayable
Change-Id: I71e5e3481aa2a3d4b26726e09e77dc4e64fbaf0b
Merged-In: Iccfac35e78219d499506ac0886f1872a7d70f846
1 file changed
tree: 1ad3c959ac4d18d96545ce68748ab0d42686cbd0
  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.