Revert "JNI: no longer -keeping all native methods"
This reverts commit f63467c4ae0cdeefa680125af4c518fd7306da09.
Reason for revert: Broke internal chrome_apk
Original change's description:
> JNI: no longer -keeping all native methods
>
> Now that manual JNI registration is an edge case and not used for
> anything we actually ship, it's worth it to conditionally not keep JNI
> in cases where we aren't doing manual registration.
>
> DFMs which manually register must ensure they actually use all their
> JNI or else they will have errors while manually registering.
>
> Bug: 688465
> Change-Id: I0e360dad777d3d476ef71dd8ffffee198c7a5703
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4424730
> Reviewed-by: Bo Liu <boliu@chromium.org>
> Commit-Queue: Sam Maier <smaier@chromium.org>
> Code-Coverage: Findit <findit-for-me@appspot.gserviceaccount.com>
> Owners-Override: Sam Maier <smaier@chromium.org>
> Reviewed-by: Andrew Grieve <agrieve@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1132199}
No-Try: true
Bug: 688465, 1434861
Change-Id: I8e737d530b596a44e5bd61c8e7df8603851588f7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4452566
Owners-Override: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1132882}
CrOS-Libchrome-Original-Commit: 4672e0f9d44bf2fcfa952badcd1386f5b9349e8a
2 files changed
