| commit | 80f7ccc6fc41fb9267d35e9fd79006710ae7c52e | [log] [tgz] |
|---|---|---|
| author | Muhammad Qureshi <muhammadq@google.com> | Tue Jun 01 21:07:30 2021 -0700 |
| committer | Muhammad Qureshi <muhammadq@google.com> | Tue Jun 01 21:30:49 2021 -0700 |
| tree | 9b8e37a5f0908fef0cace04982d049996127a9a7 | |
| parent | 9f1f0d8423727fbc712d6027e433d52ac0519594 [diff] |
Add libkll to allowed_deps Add libkll dependency to statsd. Note: libkll itself lives inside statsd apex and is also updatable along with statsd. > How big is the binary size increase for affected APEXes? +120 KB > Is the new dependency committed to support previous platform releases? > note that you have to support all the releases starting from the > minSdkVersion value you are declaring Yes, dependency is present in the statsd apex. > 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? Dependency has its own tests and integration tests with statsd being added as well in follow-up CLs. Bug: 185569933 Bug: 179823717 Test: m Change-Id: Ib826354cd8882632ea6ab297e5fdb81bfbaf8519
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.