| commit | 6bd30073a5236929709f6161cca80fda8d75e436 | [log] [tgz] |
|---|---|---|
| author | Sahana Rao <sahanas@google.com> | Wed May 12 20:47:05 2021 +0100 |
| committer | Abhijeet Kaur <abkaur@google.com> | Mon Jun 21 16:16:33 2021 +0000 |
| tree | c41fd2fab3e0df6f324c2dd3b5e11288a6bf0be4 | |
| parent | c347459cc862dc010b8c28251d62bef5de5317aa [diff] |
Add Glide to allowed_deps > How big is the binary size increase for affected APEXes? 8192 bytes > 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 > Is the new dependency being developed AOSP-first or internal? Glide dependency is AOSP-first, using the dependency to develop an internal project. > What’s the testing strategy for the new dependency? Does it have its > own tests, and are you adding integration tests? We will be adding integration and manual tests for the image loading experience. Bug: 185801129 Test: Build Change-Id: Icebf6363a0a2b1a8811cad909d4b3274638c7021
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.