Add NetworkStackApi32Shims to allowed_deps for NetworkStack.
As documented on the build rule "API 32" is not technically correct and
should be "in-progress API", but that naming has always avoided renames
at SDK finalization time.
The new target is used in development NetworkStack builds that are not
pushed to released devices (NetworkStackNext) to allow it to use
non-finalized APIs.
Bug: 189581241
Test: m
Merged-In: Ie274b4a1ea66bbbe26c7d7a78c90a19a746ea84e
Change-Id: Ie274b4a1ea66bbbe26c7d7a78c90a19a746ea84e
Add NetworkStackApi32Shims to allowed_deps for NetworkStack.
As documented on the build rule "API 32" is not technically correct and
should be "in-progress API", but that naming has always avoided renames
at SDK finalization time.
The new target is used in development NetworkStack builds that are not
pushed to released devices (NetworkStackNext) to allow it to use
non-finalized APIs.
Ignore-AOSP-First: cherry-pick prepared separately
Bug: 189581241
Test: m
Change-Id: Ie274b4a1ea66bbbe26c7d7a78c90a19a746ea84e
This bumps the version embedded into modules to 1, which the
SdkExtensions module will require to set extension version 1.
Bug: 188787081
Test: CtsSdkExtensionsTestCases & sdkextensions_e2e_tests
Change-Id: I94e1cba76a7f50ba6531ca65830d20819600d34d
Add visibility of the sdkinfo proto, as well as an enum for the module
to be used by SdkExtensions.
Bug: 188787081
Test: m com.android.conscrypt and inspect it
Change-Id: If8655c3328597580408a87e4c6dc4f92547a57e9
Those dependencies have already been allowlisted in sc-mainline-prod in
ag/13663075.
Bug: 180441353
Change-Id: Id8e04de2432f6415ca6c139df53be78c6fc437d6
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
dist_group replaces owner and the default is going to change, set it
to the current default "android" for module java_sdk_libraries.
Bug: 186723288
Test: m checkbuild
Change-Id: Id4d20471a8106718fb1529f5c83c9ca5ffb2a569
Merged-In: Id4d20471a8106718fb1529f5c83c9ca5ffb2a569
(cherry picked from commit 8573dc4a41)
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
dist_group replaces owner and the default is going to change, set it
to the current default "android" for module java_sdk_libraries.
Bug: 186723288
Test: m checkbuild
Change-Id: Id4d20471a8106718fb1529f5c83c9ca5ffb2a569
Add visibility of the sdkinfo proto, as well as an enum for the module
to be used by SdkExtensions.
Bug: 188787081
Test: m com.android.scheduling and inspect it
Change-Id: I5727e361b79ab0860d692261bde5f0b54279f791
