| commit | 06f3de2cf990e6a136774521cdbc2eef98d99cde | [log] [tgz] |
|---|---|---|
| author | Yan Yan <evitayan@google.com> | Tue Feb 02 21:38:51 2021 -0800 |
| committer | Yan Yan <evitayan@google.com> | Thu Feb 04 13:31:51 2021 -0800 |
| tree | 069e888e61403171fa1a8090d3c993d32e95744d | |
| parent | acc75d58c3a2211bfc75c50f11ef399d46ace4a8 [diff] |
Jarjar ike-tests and change test code's package Convert IKE as part of SDK will cause two problems in unit tests: - Adding IKE API stubs to android SDK stub will results in the API stubs overshadowing the IKE sources during compile time. As the result, unit tests will fail to compile with errors in finding non-API symbols - Putting IKE in BCP will prevent unit test code from accessing package protected symbols in IKE. Because the IKE jar in BCP gets higher priority than the ike_test jar loaded by the unit test application class loader, and thus causing the test code and production code loaded by two different class loaders. When test code is loaded by a different class loader, if it has the same package name with the production code, it cannot access any package protected items in the production code. Two solve this two problems, this CL: - jarjar ike_test to change it's package - also changes test package according to the jarjared library package There will be a followup CL to fix the CTS tests Bug: 177266501 Test: FrameworksIkeTests, verified with aosp/1573066(Allow IKE in BCP) Change-Id: I8c4ee5fc883198af768ce0787bb15385eea91632