| commit | ff68d0b0b9a9f995d8e15af92eced5c26c79487b | [log] [tgz] |
|---|---|---|
| author | Yabin Huang <yabinh@google.com> | Wed Jun 02 19:48:00 2021 -0700 |
| committer | Yabin Huang <yabinh@google.com> | Thu Jun 03 18:30:58 2021 +0000 |
| tree | 50709e6f53cfd599d686c1517c427f1e00cee07a | |
| parent | 0d974ddb4ed8113fa94c642cee37b177029d5209 [diff] |
Add car-rotary-lib to allowed dependencies list The new library is extracted from the existing car-ui-lib. It contains rotary specific code, which is already used by apps supporting rotary. > How big is the binary size increase for affected APEXes? It doesn't increase the size. In fact, it reduces the size if an app wants to support rotary but doesn't want to use the whole car-ui-lib. > Is the new dependency committed to support previous platform releases? Yes. > Is the new dependency being developed AOSP-first or internal? AOSP-first. > What’s the testing strategy for the new dependency? > Does it have its own tests, and are you adding integration tests? It has its own tests, such as FocusParkingViewTest. Bug: 188915160 Test: make Change-Id: Ie7b10416f845c35a19309c5091a394d65c0efe40
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.
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.