Fix dependencies of packages that target earlier releases
A previous change added legacy-android-test as a static dependency to
all packages that build against the current, test_current or
system_current and failed to compile when the junit and android.test
classes were removed from the API. Unfortunately, those changes did not
take into account that some of those packages target earlier API
versions and so will always have the classes available at runtime.
This change replaces those static dependencies with dynamic dependencies
for any package that targets an earlier API version. The file changes
were made automatically by a tool that constructed and then analyzed a
full dependency graph of all the Android Java modules. The individual
changes were checked manually to ensure that the changes matched the
intent. The affected modules were built against an API with the junit
and android.test classes removed. Any issues found during this process
resulted in either the tool being updated to address the issue or a
separate change being made to fix an existing problem with the build. A
sample of the affected packages were run to ensure that they worked as
expected at runtime; no issues were found during testing.
The following change descriptions were generated automatically and so
may be a little repetitive. They are provided to give the reviewer
enough information to check the comments match what has actually been
changed and check the reasoning behind the changes.
* apps/CtsVerifier/Android.mk
Added 'legacy-android-test' to LOCAL_JAVA_LIBRARIES because module
CtsVerifier builds against 'LOCAL_SDK_VERSION := test_current' and
uses classes from package android.test (possibly indirectly) so
will no longer compile once they are removed from the API.
It was not added to LOCAL_STATIC_JAVA_LIBRARIES because
CtsVerifier's manifest file (AndroidManifest.xml) targets API level
26 and uses the android.test.runner library which will provide the
classes dynamically at runtime.
* hostsidetests/appsecurity/test-apps/UsePermissionApp22/Android.mk
Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
because CtsUsePermissionApp22's manifest file (AndroidManifest.xml)
targets API level 22 and dynamically includes the
android.test.runner library at runtime so there is no point in
statically including the classes.
Added 'legacy-android-test' to LOCAL_JAVA_LIBRARIES because module
CtsUsePermissionApp22 uses classes from package android.test
(possible indirectly) and needs them available at compile time.
Dependency 'legacy-android-test' is used instead of
'android.test.runner' because the latter will conflict with
dependencies on junit.
* hostsidetests/appsecurity/test-apps/UsePermissionApp23/Android.mk
Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
because CtsUsePermissionApp23's manifest file (AndroidManifest.xml)
targets API level 23 and dynamically includes the
android.test.runner library at runtime so there is no point in
statically including the classes.
Added 'legacy-android-test' to LOCAL_JAVA_LIBRARIES because module
CtsUsePermissionApp23 uses classes from package android.test
(possible indirectly) and needs them available at compile time.
Dependency 'legacy-android-test' is used instead of
'android.test.runner' because the latter will conflict with
dependencies on junit.
* hostsidetests/devicepolicy/app/AccountCheck/Auth/Android.mk
Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
because CtsAccountCheckAuthApp's manifest file
(AndroidManifest.xml) targets API level 25 and dynamically includes
the android.test.runner library at runtime so there is no point in
statically including the classes.
Added 'legacy-android-test' to LOCAL_JAVA_LIBRARIES because module
CtsAccountCheckAuthApp builds against 'LOCAL_SDK_VERSION :=
test_current' and uses classes from package android.test (possibly
indirectly) so will no longer compile once they are removed from
the API.
* hostsidetests/devicepolicy/app/DeviceAdmin/api23/Android.mk
Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
because CtsDeviceAdminApp23's manifest file (AndroidManifest.xml)
targets API level 23 and dynamically includes the
android.test.runner library at runtime so there is no point in
statically including the classes.
Added 'legacy-android-test' to LOCAL_JAVA_LIBRARIES because module
CtsDeviceAdminApp23 builds against 'LOCAL_SDK_VERSION := current'
and uses classes from package android.test (possibly indirectly) so
will no longer compile once they are removed from the API.
* hostsidetests/devicepolicy/app/DeviceAdmin/api24/Android.mk
Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
because CtsDeviceAdminApp24's manifest file (AndroidManifest.xml)
targets API level 24 and dynamically includes the
android.test.runner library at runtime so there is no point in
statically including the classes.
Added 'legacy-android-test' to LOCAL_JAVA_LIBRARIES because module
CtsDeviceAdminApp24 builds against 'LOCAL_SDK_VERSION := current'
and uses classes from package android.test (possibly indirectly) so
will no longer compile once they are removed from the API.
* hostsidetests/devicepolicy/app/DeviceAndProfileOwner/api23/Android.mk
Added 'legacy-android-test' to LOCAL_JAVA_LIBRARIES because module
CtsDeviceAndProfileOwnerApp23 builds against 'LOCAL_SDK_VERSION :=
test_current' and uses classes from package android.test (possibly
indirectly) so will no longer compile once they are removed from
the API.
It was not added to LOCAL_STATIC_JAVA_LIBRARIES because
CtsDeviceAndProfileOwnerApp23's manifest file (AndroidManifest.xml)
targets API level 23 and uses the android.test.runner library which
will provide the classes dynamically at runtime.
* hostsidetests/devicepolicy/app/DeviceAndProfileOwner/api25/Android.mk
Added 'legacy-android-test' to LOCAL_JAVA_LIBRARIES because module
CtsDeviceAndProfileOwnerApp25 builds against 'LOCAL_SDK_VERSION :=
test_current' and uses classes from package android.test (possibly
indirectly) so will no longer compile once they are removed from
the API.
It was not added to LOCAL_STATIC_JAVA_LIBRARIES because
CtsDeviceAndProfileOwnerApp25's manifest file (AndroidManifest.xml)
targets API level 25 and uses the android.test.runner library which
will provide the classes dynamically at runtime.
* hostsidetests/devicepolicy/app/LauncherTests/Android.mk
Replaced 'android.test.runner' with 'legacy-android-test' in
LOCAL_JAVA_LIBRARIES because module CtsLauncherAppsTests builds
against 'LOCAL_SDK_VERSION := current' and uses classes from
package android.test (possibly indirectly) so will no longer
compile once they are removed from the API.
Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
because CtsLauncherAppsTests's manifest file (AndroidManifest.xml)
targets API level 25 and dynamically includes the
android.test.runner library at runtime so there is no point in
statically including the classes.
* hostsidetests/devicepolicy/app/LauncherTestsSupport/Android.mk
Removed android.test.runner from LOCAL_JAVA_LIBRARIES because
module CtsLauncherAppsTestsSupport does not use any classes from
android.test.runner at compile time.
* hostsidetests/dumpsys/apps/ProcStatsHelperApp/Android.mk
Removed android.test.runner from LOCAL_JAVA_LIBRARIES because
module CtsProcStatsHelperApp does not use any classes from
android.test.runner at compile time.
* tests/tests/accounts/Android.mk
Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
because CtsAccountManagerTestCases's manifest file
(AndroidManifest.xml) targets API level 26 and dynamically includes
the android.test.runner library at runtime so there is no point in
statically including the classes.
Added 'legacy-android-test' to LOCAL_JAVA_LIBRARIES because module
CtsAccountManagerTestCases builds against 'LOCAL_SDK_VERSION :=
current' and uses classes from package android.test (possibly
indirectly) so will no longer compile once they are removed from
the API.
* tests/tests/calendarcommon/Android.mk
Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
because CtsCalendarcommon2TestCases's manifest file
(AndroidManifest.xml) targets API level 15 and dynamically includes
the android.test.runner library at runtime so there is no point in
statically including the classes.
Added 'legacy-android-test' to LOCAL_JAVA_LIBRARIES because module
CtsCalendarcommon2TestCases builds against 'LOCAL_SDK_VERSION :=
current' and uses classes from package android.test (possibly
indirectly) so will no longer compile once they are removed from
the API.
* tests/tests/dpi2/Android.mk
Added 'legacy-android-test' to LOCAL_JAVA_LIBRARIES because module
CtsDpiTestCases2 builds against 'LOCAL_SDK_VERSION := current' and
uses classes from package android.test (possibly indirectly) so
will no longer compile once they are removed from the API.
It was not added to LOCAL_STATIC_JAVA_LIBRARIES because
CtsDpiTestCases2's manifest file (AndroidManifest.xml) targets API
level 3 and uses the android.test.runner library which will provide
the classes dynamically at runtime.
* tests/tests/provider/Android.mk
Replaced 'android.test.runner' with 'android.test.mock' and
'legacy-android-test' in LOCAL_JAVA_LIBRARIES because module
CtsProviderTestCases uses classes from packages android.test and
android.test.mock (possible indirectly) and needs them available at
compile time.
Dependency 'legacy-android-test' is used instead of
'android.test.runner' because the latter will conflict with
dependencies on junit.
Dependency 'android.test.mock.sdk' is used instead of
'android.test.mock' because module CtsProviderTestCases builds
against internal jars not the API and so should use libraries that
build against internal jars not the API.
Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
because CtsProviderTestCases's manifest file (AndroidManifest.xml)
targets API level 21 and dynamically includes the
android.test.runner library at runtime so there is no point in
statically including the classes.
* tests/tests/selinux/selinuxTargetSdk/Android.mk
Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
because CtsSelinuxTargetSdkTestCases's manifest file
(AndroidManifest.xml) targets API level 25 and dynamically includes
the android.test.runner library at runtime so there is no point in
statically including the classes.
Added 'legacy-android-test' to LOCAL_JAVA_LIBRARIES because module
CtsSelinuxTargetSdkTestCases builds against 'LOCAL_SDK_VERSION :=
current' and uses classes from package android.test (possibly
indirectly) so will no longer compile once they are removed from
the API.
Bug: 30188076
Test: make checkbuild and ran a sample of tests
Change-Id: I4744db5f5c9b33b2cb13e8a0edc46881d3aa8aae
16 files changed