summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Duffin <paulduffin@google.com>2017-12-05 18:36:56 +0000
committerPaul Duffin <paulduffin@google.com>2017-12-05 18:36:56 +0000
commitd49326f48c105c73fc14eae3c9b222e5ba3e42ee (patch)
tree55ce011bed330ce02f3accdaf49b862c489d5c57
parente426de20f9eb216ec1ebcd559fbfc8010476f3f7 (diff)
downloadlowpan-d49326f48c105c73fc14eae3c9b222e5ba3e42ee.tar.gz
Flatten dependency hierarchy of legacy-android-test
Previous changes statically included legacy-android-test in preparation for removing android.test.* and junit.* classes from the android.jar. Unfortunately, that lead to duplicate classes between APKs and the bootclasspath which caused build problems (Proguard) and also runtime problems (when targeting and running on older releases). Switching from statically including the classes to using the runtime libraries cannot be done in one step because legacy-android-test is statically included in libraries which are used in many APKs and so removing it from those libraries requires that all APKs be updated at once. Doing that atomically across dozens of projects is not practical. This change modifies APKS that statically include the legacy-android-test library indirectly. * If the APK manifest uses the android.test.runner library then the APK is modified to stop statically including legacy-android-test and instead build against android.test.base/mock/runner libraries instead. * Otherwise, the APK statically includes legacy-android-test. Also, any libraries that statically include are modified to stop statically including it and if it has source dependencies on the classes is changed to build against the android.test.base/mock/runner libraries. 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. * libandroid_net_lowpan/tests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because FrameworksLowpanApiNativeTests's source depends on its classes and because of these changes they are no longer present on the compilation path. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that FrameworksLowpanApiNativeTests specifies in its manifest. Bug: 30188076 Test: make checkbuild Change-Id: Ie345cefb69a7afcd2486c8d245148549d791fb97
-rw-r--r--libandroid_net_lowpan/tests/Android.mk2
1 files changed, 1 insertions, 1 deletions
diff --git a/libandroid_net_lowpan/tests/Android.mk b/libandroid_net_lowpan/tests/Android.mk
index ee44bc5..7bc8dbe 100644
--- a/libandroid_net_lowpan/tests/Android.mk
+++ b/libandroid_net_lowpan/tests/Android.mk
@@ -82,7 +82,7 @@ LOCAL_JNI_SHARED_LIBRARIES += \
libhwbinder \
android.hidl.token@1.0
-LOCAL_JAVA_LIBRARIES := android.test.runner
+LOCAL_JAVA_LIBRARIES := android.test.runner android.test.base
LOCAL_PACKAGE_NAME := FrameworksLowpanApiNativeTests
LOCAL_COMPATIBILITY_SUITE := device-tests