Fix NoSuchMethodError in mvc-annotation-commons&change deprecated method

[CzyerChen]

Fix NoSuchMethodError in mvc-annotation-commons&change deprecated method

• Add a unit test to verify that the fix works.
  current test scenarios(spring-4.3.x-scenario, spring-6.x-scenario) passed.

• Explain briefly why the bug exists and how to fix it.

• If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes [Bug] mvc-annotation-commons NoSuchMethodError ServerHttpRequest.getMethodValue() skywalking#11652.

• Update the CHANGES log.

[wu-sheng]

I want to double-check, this test has covered 3.2.18.RELEASE, so, only 3.2.0 had the bug, but 3.2.8 is OK?

[CzyerChen]

I want to double-check, this test has covered 3.2.18.RELEASE, so, only 3.2.0 had the bug, but 3.2.8 is OK?

I can write a scenario with version 3.2.18.RELEASE and test again locally.

[wu-sheng]

The link I provided, it has tested 3.1.4.RELEASE, 3.2.18.RELEASE, 4.0.9.RELEASE, check this, https://github.com/apache/skywalking-java/blob/main/test/plugin/scenarios/spring-3.1.x-scenario/support-version.list.

What I want to confirm with you is, is this test covers your scenario if we add 3.2.0.xx into that? Or 3.2.18 is still having this bug just not covered by the test.

[CzyerChen]

The link I provided, it has tested 3.1.4.RELEASE, 3.2.18.RELEASE, 4.0.9.RELEASE, check this, https://github.com/apache/skywalking-java/blob/main/test/plugin/scenarios/spring-3.1.x-scenario/support-version.list.

What I want to confirm with you is, is this test covers your scenario if we add 3.2.0.xx into that? Or 3.2.18 is still having this bug just not covered by the test.

• SpringBoot version upgrade to 3.2.0 and Spring version upgrade to 6.1.1, then getMethodValue removed and caused NoSuchMethodError, so i want to commit this change.
• I add Spring version 6.1.0/6.1.1 support-version into spring-6.x-scenario, change dependency versions in pom.xml to support Spring 6.x(springboot2+spring5 dependency management for 2.7.x with springboot3+spring6 dependency management for 3.0.x .
• Upgrade from springboot3.1.x+spring6.0.x to springboot3.2.x+spring6.1.x, our testcase spring-6.x-scenario is a spring project, not a springboot project, so i follow the issue http request parameter error to change maven compile config, and it works.
• I passed spring-6.x-scenario locally.

[wu-sheng]

So, only this is using SpringBoot 3.2.0, which was failing before the fix, am I getting your idea correctly?

[CzyerChen]

yes, I tracd my own springboot project in 3.2.0(Spring 6.1.1), and find SpringMVC node missing, but springboot project in 3.1.6(Spring 6.0.14) works.