RFR: 8287745 jni/nullCaller/NullCallerTest.java fails with "exitValue = 1"

[David Holmes]

On Mon, 6 Jun 2022 15:56:47 GMT, Tim Prinzing <tprinzing at openjdk.org> wrote:

> The idea was to reduce duplicate code. Changing to use objects to encapsulate the up calls got rid of a lot of repeated code and made things simpler and clearer. Objects are created with the class, method, and signature strings and then calls can be made and the the error reporting has a context. It was simply easier to do in c++ and there was no reason not to use it.

Fair enough. At least we will now have a good example of what is needed to build a C++ test like this.

-------------

PR: https://git.openjdk.java.net/jdk/pull/9010