JDK contains multiple libraries for parsing, generating, and transforming class files. Classfile API project goal is to provide JDK-based, accurate, complete, up-to-date, performant API for reading, writing and transforming Java class files.

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.

This is an umbrella issue to collect and monitor JDK use cases; each under individual sub-task.