RFR: 8328111: Convert Runtime tests to use the ClassFile API instead of ASM [v17]

[Chen Liang]

On Mon, 25 Mar 2024 10:36:36 GMT, Oussama Louati <duke at openjdk.org> wrote:

>> The main goal pull request migrate the existing tests to utilize the new ClassFile API instead of the ASM library. The use of ASM has served us well in the past, but maintaining it has its costs and limitations.
>> 
>> ### **Cost of Maintaining ASM Library:**
>> 
>> - _Risk of Changes:_ The ASM library is an external dependency, and updates or changes in its APIs can introduce unforeseen issues or require significant code modifications in our tests.
>> - _Lack of Reviewers:_ As the ASM library evolves, finding reviewers familiar with its intricacies becomes challenging, leading to delays in reviewing and merging changes.
>> 
>> ### **Reasons for Migration:**
>> 
>> - _Stability and Consistency:_ Utilizing the ClassFile API ensures stability and compatibility with the Java platform, reducing the risk of compatibility issues due to external library changes.
>> - _Sustainability:_ The ClassFile API is a standard part of Java, making it easier to find reviewers and maintain code consistency across test suites.
>> - _Future Compatibility:_ As Java evolves, relying on native Java APIs like the ClassFile API ensures future compatibility and reduces technical debt.
>> 
>> ### **Concerns Addressed:**
>> 
>> - Risk of Changes: By migrating to a standard Java API, we mitigate the risks associated with external library changes and ensure smoother maintenance and updates in the future.
>> - Backporting and Compatibility: The use of native Java APIs allows for easier backporting of test fixes and ensures compatibility across Java versions, including preview releases.
>> 
>>> **Please note:** We won't integrate this PR until we've fully finalized the ClassFile API and all tests utilize it.
>
> Oussama Louati has updated the pull request incrementally with two additional commits since the last revision:
> 
>  - use Exception thrown as the old code
>  - convert BootstrapMethodErrorTest to use the classfile API

test/hotspot/jtreg/runtime/invokedynamic/BootstrapMethodErrorTest.java line 63:

> 61:             }
> 62:             catch (Throwable th) {
> 63:                 th.printStackTrace();

Why? printing stack trace is not recommended as it may lead to the throwable being ignored. Please restore the previous code here.

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

PR Review Comment: https://git.openjdk.org/jdk/pull/18271#discussion_r1537762770