Age | Commit message (Collapse) | Author |
|
Bug: 18222974
Change-Id: Ie39d49e9dfe90f20b6eb5d28009313781eac8e01
|
|
Bug: 12492817
In L-preview, we temporarily used GServices to read DRP key. remove
this mechanism and embed the key into the apk.
Change-Id: Id94ac1348e615a8fa5a21c9e4a5bd43399821e46
|
|
BUG: 11505352
Change-Id: I1f601605943738dd207a6ba267063c00527565de
|
|
Also clean up unneccesary or.chromium.* classes, as proguard
runs after JARJAR.
Change-Id: I24d379658b8d683fe05a244b573056b8f4f2efde
|
|
Change-Id: Ib74f8d7a46a25b94a1684c9b05ee2ccafbdcc4ff
|
|
We need to keep methods that are tagged @JavascriptInterface as these
are discovered by reflection at runtime and used to create JS bindings.
Stripping these was breaking ChromeVox; works with this change.
Bug: 10766751
Change-Id: I1c0b9a855d99c812bd4a3f05e6373c5b2fe045a4
(cherry picked from commit d32e258033d74fb551442b10547215de443be05c)
|
|
Explicitly keep the classes that proguard generates warnings for.
These classes are parameters to methods of entry points.
Change-Id: I08bced014af760a9b871ddb84b6225e02695cc24
|
|
Missed one of the package renames in the previous CL to fix the proguard
config.
Change-Id: If917b11890c3cf1b2b8e853b7d81a757744f5dc6
|
|
The jarjar rules got changed to rename packages differently, causing
proguard rules to no longer match. Update them to reflect the new
package names.
Change-Id: Ibda2e796106eaf3965d5b56496cf4a55915d7816
|
|
When building webviewchromium.jar, use jarjar to rename classes in
accordance with the rules file checked into the Chromium tree. The same
rules must be used on both sides as the JNI generator needs to also
rename its class references when building native code. The proguard
rules must also reference the renamed classes, as jarjar runs before
proguard - we keep both sets of names in the proguard config so that
jarjar can be disabled if needed without disabling proguard.
Change-Id: Ib5675ead752c5c3cd62c9ae7bbf84106f4454288
|
|
1) We should explicitly keep the native methods in
com.android.webview.chromium as well, since the plat_support library
will crash if they are removed. This wasn't actually broken as they were
references anyway, but being explicit is better.
2) Using a single "keep" statement for the org.chromium JNI interface
causes all classes in that package to be kept even if they don't have
JNI members. Instead, we should have a separate "keepclasseswithmembers"
for each of the kinds of JNI interface to keep only classes that have
at least one of those methods. This allows a few more classes to be
removed entirely (along with their constructors) and prunes a small
amount of extra code as a result.
Change-Id: I7ce4dd7bdca36af49a306838bb567317e5314f4f
|
|
Add a proguard config file with a minimal working set of flags to keep
the code we actually need. This commit does not enable proguard yet.
Change-Id: If578bbd2473113220b2731d84e6317f5b79e4443
|