diff options
author | Paul Duffin <paulduffin@google.com> | 2017-12-05 18:36:56 +0000 |
---|---|---|
committer | Paul Duffin <paulduffin@google.com> | 2017-12-05 18:36:56 +0000 |
commit | acfab7fa0bae891b38fc622932427b194e82c1f2 (patch) | |
tree | 502998deb9da09f8dadc91d1c67904cd60e02781 /tck-android | |
parent | 23e3250ef19112142d854e999487918f970dc034 (diff) | |
download | objenesis-acfab7fa0bae891b38fc622932427b194e82c1f2.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.
* tck-android/Android.mk
Replaced 'legacy-android-test' with 'android.test.base' in
LOCAL_JAVA_LIBRARIES because ObjenesisTck's source depends on its
classes. 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
ObjenesisTck specifies in its manifest.
Bug: 30188076
Test: make checkbuild
Change-Id: I4a0a0ac4e1a9052fd7774f9687feace0ebb6304d
Diffstat (limited to 'tck-android')
-rw-r--r-- | tck-android/Android.mk | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tck-android/Android.mk b/tck-android/Android.mk index bf7ed4b..f7ea6b6 100644 --- a/tck-android/Android.mk +++ b/tck-android/Android.mk @@ -29,6 +29,6 @@ LOCAL_MODULE_TAGS := tests LOCAL_CERTIFICATE := platform LOCAL_STATIC_JAVA_LIBRARIES := objenesis-tck junit -LOCAL_JAVA_LIBRARIES := legacy-android-test +LOCAL_JAVA_LIBRARIES := android.test.base LOCAL_SRC_FILES := $(call all-java-files-under, src/main/java) include $(BUILD_PACKAGE) |