Age | Commit message (Collapse) | Author |
|
These is a conflict when using this meta tag together with Android Support
Library as it specifies a different version.
Bug: 38037855
Test: ./gradlew dist
Change-Id: If23423bcbf93a4cd4a0b5e3a5593d1f563756933
|
|
1) am: 49f3d944cf am: 8c2d2db0e3 am: 49cff4d6d9
am: eaeb6e4c29
Change-Id: I4f4ce2e70d6d22825f17b5436d89891a9fc7381f
|
|
1) am: 49f3d944cf am: 8c2d2db0e3
am: 49cff4d6d9
Change-Id: Ief63a0d2759860129bc140bad1e55d878f4b1240
|
|
1) am: 49f3d944cf
am: 8c2d2db0e3
Change-Id: I92e048d574e3a2b638d33ceee46c979398859791
|
|
am: 49f3d944cf
Change-Id: I4d68161e66b04863775fe245bc5f1dba5025b799
|
|
In preparation for removing junit and android.test classes from
the Android API this change adds explicit dependencies on junit
and/or legacy-android-test to ensure that modules will compile
properly once it is removed.
Care was taken to ensure that any targets that depended,
directly or indirectly, on android-support-test did not also
depend on junit or hamcrest as they conflict with the versions
embedded within android-support-test.
Bug: 30188076
Test: make checkbuild
Change-Id: If3c3566dd730a0df046ba1733bf8a20b29c9e335
|
|
In ag/1971845 we accidentally changed artifactId of multidex and
multidex-instrumentation to support-multidex and support-multidex-instrumentation.
This change undoes that change.
Bug: 36122649
Test: ./gradle clean dist now produces correct repo zip
Change-Id: I110446366250315be0d04929b333d47c3fba0d2c
|
|
of just aar."
|
|
Bug: 36122649
Test: ./gradlew clean dist
Change-Id: Ia7ace388ba72abff4a167552628b892cae024f7c
|
|
This change will trigger ub-multidex-master to start building for the first time.
Change-Id: I1b3bb509b25a63311fa70aae28fb2d2b2ab9c69d
|
|
am: 5ccdd930f0
Change-Id: I1352525730454a258b6cd5a51c2577c7db665944
|
|
am: 668b6077de
Change-Id: Ic9a989e69350b0e8414537aeb2003ba1847a6dec
|
|
am: 93728d8ae0
Change-Id: I1415b75446e18bfd1bf19a5646cad40adde040db
|
|
Bug: 36122649
Test: ./gradlew dist test connectedAndroidTest
Change-Id: I79578f683146a3ea16521cd090d113698a14c5f5
|
|
Bug: 35796382
Test: N/A
Change-Id: I7a36e9223b010a04a1d2ea28914d0b502dd7f61e
|
|
2422a2eb3d
am: 4a2df94e21
Change-Id: Id89f28382eb25d81dce26edcc2e3a12fe6e0238d
|
|
am: 2422a2eb3d
Change-Id: Ied383048c8cc3b94d0fe33628cb39ff9eb71b4ed
|
|
am: 20f0cdc308
Change-Id: I7d84966360e8283d7b24c6009f5fd79ed2dbc5b5
|
|
am: 9958145a97
Change-Id: Iac3e4fef6a30d8085ab29609df92e0cca1800da0
|
|
221296887a
am: d3f4428cfd
Change-Id: Idc5e7387402151453f3a4ea75300e9c9c892e9b3
|
|
am: 221296887a
Change-Id: Ica275e0ae0c3dd2d3efa9ca3f75fd5b95f220ccd
|
|
am: 8c46dd3b3f
Change-Id: I914ec257f75aa6b6b84984659fc24445c6d8fe60
|
|
am: fe10f9fd25
Change-Id: I529bc3ae057f9fef4cb7c64c3e490a773e1ec0c2
|
|
Protect extracted dex files from modifications by checking their crc and
modification time. In case of change, proceed to a new extraction.
Those checks are replacing the check of the zip integrity by
opening it with a ZipFile.
Test: SupportMultidexHostTest (from tradefed)
Bug: 32159214
Change-Id: I09aa01550782f5f550bee6fc91709455e82c1057
|
|
4207787110
am: 1aad735e08
Change-Id: I4d6975d40e63b713e23ad143f3b2462a98fecb14
|
|
am: 4207787110
Change-Id: I7a7c3174d6264a8b788e2a08eacf378b78abd24b
|
|
am: 45e77758d4
Change-Id: I5eaa02b87dfbd14ab11d1c9be18b8768e8e5523f
|
|
am: f5832474eb
Change-Id: I16b9a24cec6cde11714f4df2032324045996cd39
|
|
The check is unnecessary in MultiDex.install because it was already done
by MultiDexExtractor.load. The retry on bad extraction is also included
in MultiDexExtractor.load so it was redundant too.
Test: SupportMultidexHostTest (from tradefed)
Change-Id: I877a99db0e0c562ac47a7c5c87d7f3e1d70884e6
|
|
This is a poor protection from some attack against application that
would be made to overwrite their extracted secondary dex files.
The protection is poor because marking the dex files read only will
protect only some applications depending on their implementation.
Test: MultiDexLegacyVersionedTestApp
Bug: 32159214
Change-Id: I88c6fc72284f4e0b832dc4d840c9c636a1234638
|
|
d288c44654 am: 0b80313260
am: 708a59cce4
Change-Id: I5360a7f9e03f4eb47c288bd19a62c315973f6398
|
|
am: 5504711f87
Change-Id: Ib530e83309aae0a0a0c054dc2e8879c0ca7c22f3
|
|
d288c44654
am: 0b80313260
Change-Id: I0d5772c4ce26e9f1b3c7b8d517ed962345cfcf02
|
|
am: 7bf8f6f48f
Change-Id: I05979b27ded1989f5f8cef3e8a9f503e590d1c72
|
|
am: d288c44654
Change-Id: If625dc1bae06d2f8fc0e8203c984df1db2f537e7
|
|
am: b703c32e27
Change-Id: I480aed8ab0808015d14ef114f20eb0004bc35ada
|
|
am: b504c8f1b2
Change-Id: I97e7c14ab15cf0af6e61410ea26164447300297b
|
|
am: 87738871b5
Change-Id: Ia0fe8f8b038b38cb58906727a4f79b8a32ec5298
|
|
|
|
Due to package install races it is possible for a process to be started from an
old apk even though that apk has been replaced. Querying for ApplicationInfo by
package name may return information for the new apk, leading to a runtime with
the old main dex file and new secondary dex files. This leads to various
problems like ClassNotFoundExceptions. Using context.getApplicationInfo()
should result in the process having a consistent view of the world (even if it
is of the old world). The package install races are eventually resolved and old
processes are killed.
Test: Passes Google Play services tests
Change-Id: I95257d851eb678c55a19e731183f7add2b540615
|
|
Temp files are removed unconditionally in a finally block following extraction.
However, if the process is killed during extraction this finally block will not
run. Because temp files started with extractedFilePrefix, they wouldn't be
cleaned up in prepareDexDir(). This change ensures that prepareDexDir() will
remove any existing temp files before extraction begins.
Bug: 27769642
Bug: 33718827
Test: Passes Google Play services tests
Change-Id: I803ba2c7234801551d36cbbe2941eeaa986d31f8
|
|
Due to package install races it is possible for a process to be started from an
old apk even though that apk has been replaced. Querying for ApplicationInfo by
package name may return information for the new apk, leading to a runtime with
the old main dex file and new secondary dex files. This leads to various
problems like ClassNotFoundExceptions. Using context.getApplicationInfo()
should result in the process having a consistent view of the world (even if it
is of the old world). The package install races are eventually resolved and old
processes are killed.
Test: Passes Google Play services tests
Change-Id: I95257d851eb678c55a19e731183f7add2b540615
|
|
Temp files are removed unconditionally in a finally block following extraction.
However, if the process is killed during extraction this finally block will not
run. Because temp files started with extractedFilePrefix, they wouldn't be
cleaned up in prepareDexDir(). This change ensures that prepareDexDir() will
remove any existing temp files before extraction begins.
Bug: 27769642
Bug: 33718827
Test: Passes Google Play services tests
Change-Id: I803ba2c7234801551d36cbbe2941eeaa986d31f8
|
|
am: 282eaa7b17
Change-Id: If88c07584b9bc2f2878504c4622f8233bf64099b
|
|
am: 91ff19c89b
Change-Id: I3fae80ab5ddf1cb2666037216a26498ce81e1c62
|
|
am: 8e58f1bef2
Change-Id: I532d31d12968688c81426e175ef986d18e96a42c
|
|
am: 07bca8fb7f
Change-Id: I33264c4389947c816e20b1dfea1d65478280dcd3
|
|
- Stop collecting build id and version to allow better behavior with
incremental builds.
- Make it resistant to git errors.
Test: mm
Change-Id: I03b1e36048f92f50227cfc0e370454438bee31cf
|
|
am: 3fdcf1a004
am: 6b14ba2339
Change-Id: Id143f90c549aaca030ad6a1eb7dddba9742aede3
|
|
am: 3fdcf1a004
Change-Id: I76d7bf999e161459484eb4f576342aab2f4101c7
|