Closed warunalakshitha closed 2 weeks ago
Happens due to the JDI method invokation picks a wrong method for Class.forName()
method. With Java 21, a new method with 3 parameters is added in Class
class.
private static Class<?> forName(Module module, String name, Class<?> caller);
Since we only consider parameter count to call the Class.forName()
method, it fails with invalid JDI invocation.
This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.
- Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
- Reason/Regression - The issue has introduced a regression.
- Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
- Reason/Complex - Issue occurred due to complex scenario.
- Reason/Invalid - Issue is invalid.
- Reason/Other - None of the above cases.
Description
If we use Java 21 to run the ballerina debugger integration tests with minimum changes, tests are failing as below.
Steps to Reproduce
You can simply run the current main branch with Java 21 and skip checkstyle (-x check). Please use https://github.com/ballerina-platform/ballerina-lang/pull/43087 PR for all the changes done fixing checkstyle as well. Note: I have temporary disable debugger tests in workflow to check other test cases.
Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
-> Debugger
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response