tag 62e5314205f84448711ede1c486217265aac5e5a
tagger The Android Open Source Project <initial-contribution@android.com> Tue May 08 10:24:39 2018 -0700
object 51b18905eadbbdf201d5e3864fe854da2c5d3719

Android p preview 2

commit 51b18905eadbbdf201d5e3864fe854da2c5d3719
author Gustav Sennton <gsennton@google.com> Mon Mar 05 10:23:12 2018 +0000
committer Gustav Sennton <gsennton@google.com> Mon Mar 05 16:01:21 2018 +0000
tree 31c183ac4bc237e034b2d4fe13cf68f410d27aaa
parent cd3a69c9377b612a5f791b9f50182528f173b55b

[android_webview] Save boundary interfaces from proguard obfuscation

We need to keep the names of all boundary interface classes and methods
used by the support library and chromium to ensure their names are the
same in the support library as in the WebView APK.
However, utility classes in the boundary interface package can be
obfuscated just fine since they are not part of the boundary interface
API.

Ideally then, we will put everything that is part of the boundary
interface API in one specific package, and keep utility methods in a
sub-package, to allow for simple proguard rules (and avoid bugs where we
incorrectly keep/remove new boundary interfaces).

Bug: 809471
Change-Id: I7a700fcc50998d83bf3bfa799196477289bedb3e
Reviewed-on: https://chromium-review.googlesource.com/943504
Reviewed-by: agrieve <agrieve@chromium.org>
Reviewed-by: Richard Coles <torne@chromium.org>
Commit-Queue: Gustav Sennton <gsennton@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#540800}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 0a6e992e64dcf503e038e34a0c7952172b29d9a9