From 6741b086c7ece37b371f59c68bd80c279dc3fa5c Mon Sep 17 00:00:00 2001 From: Paul Duffin Date: Tue, 13 Jun 2017 12:28:59 +0100 Subject: 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. * tests/Android.mk Replaced 'android.test.runner' with 'legacy-android-test' in LOCAL_JAVA_LIBRARIES because module PartnerBookmarksProviderTest 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. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because PartnerBookmarksProviderTest's manifest file (AndroidManifest.xml) targets API level 14 and dynamically includes the android.test.runner library at runtime so there is no point in statically including the classes. Bug: 30188076 Test: make checkbuild and ran a sample of tests Change-Id: I16b2226c19f0112b6a51810b6cfab598004bb61c --- tests/Android.mk | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/Android.mk b/tests/Android.mk index bb20720..b509e96 100644 --- a/tests/Android.mk +++ b/tests/Android.mk @@ -24,8 +24,8 @@ LOCAL_SRC_FILES := $(call all-java-files-under, src) LOCAL_PACKAGE_NAME := PartnerBookmarksProviderTest -LOCAL_JAVA_LIBRARIES := ext android.test.runner -LOCAL_STATIC_JAVA_LIBRARIES := junit legacy-android-test +LOCAL_JAVA_LIBRARIES := ext legacy-android-test +LOCAL_STATIC_JAVA_LIBRARIES := junit LOCAL_INSTRUMENTATION_FOR := PartnerBookmarksProvider -- cgit v1.2.3