Evaluate upgrading Groovy to 5.0.0 under JDK 11 runtime constraint

[Siman-hub]

Evaluation Purpose

This PR is an extension to another PR ( #13671 ) and evaluates upgrading the Groovy engine from 4.0.x to 5.0.0 (earliest GA) with a focus on validating SkyWalking’s JDK 11 runtime compatibility guarantee.

Groovy is used as a runtime dependency in several OAP backend modules, so this change is evaluated strictly from a compatibility and policy perspective.

Verification Results

Local evaluation was performed using JDK 21 for build and JDK 11 for runtime, targeting the primary Groovy consumers (log-analyzer and meter-analyzer).

• Build Status: SUCCESS (built with JDK 21)

• Runtime Compatibility:
  Verified that the OAP distribution starts successfully on JDK 11 with Groovy 5.0.0.

  • Test: Built full distribution (-Pdist) on JDK 21, then launched OAP via oapService.bat using JDK 11.
  • Result: Server started successfully and bound ports without any UnsupportedClassVersionError or JVM compatibility failures.

• Tests Passed:

  • oap-server/analyzer/log-analyzer (LAL script parsing)
  • oap-server/analyzer/meter-analyzer (MAL script execution)

Key Findings

• No compilation issues observed in backend modules.
• No Groovy/Spock incompatibilities detected in the existing test suite.
• Groovy 5.0.0 does not introduce runtime incompatibilities with JDK 11 based on the evaluated scope.

Scope Notes

This PR is intended solely as a compatibility evaluation and does not include test refactors, additional Groovy 5.x upgrades, or behavioral changes.

[Copilot]

Pull request overview

This PR upgrades the Groovy dependency from version 4.0.15 to 5.0.0, with a focus on validating runtime compatibility under JDK 11 constraints. The author has verified that the OAP distribution builds successfully with JDK 21 and runs on JDK 11 without compatibility issues.

Changes:

• Upgrade Groovy version from 4.0.15 to 5.0.0 in the BOM

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[wu-sheng]

e2e and UT seem all good. Could you fix dependency and change log?

[wu-sheng]

Suggested change

	<groovy.version>5.0.0</groovy.version>
	<groovy.version>5.0.3</groovy.version>

We should consider latest patch version. Ref to https://mvnrepository.com/artifact/org.apache.groovy/groovy

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Groovy 5.0.0 represents a major version upgrade from 4.0.15. While the PR description indicates thorough local testing, it would be beneficial to verify that this is indeed the intended GA (General Availability) version. Groovy 5.x introduces some breaking changes from 4.x, and while the tests reportedly pass, consider documenting any behavioral differences or migration notes for future reference, especially since this affects DSL parsing in critical analyzer modules.

Suggested change

	<groovy.version>5.0.0</groovy.version>
	<groovy.version>4.0.15</groovy.version>

[Siman-hub]

I’ve addressed the requested follow-ups:

1. Updated Groovy to the latest patch version 5.0.3.
2. Updated the dependency LICENSE to reflect the Groovy version change.
3. Added the change entry to the 10.4.0 changelog.
   This PR is intentionally scoped to dependency evaluation and runtime compatibility validation. Groovy is used internally within the OAP backend, and existing unit/e2e tests cover analyzer behavior; no user-facing DSL changes or migration requirements are introduced here.

[wu-sheng]

Let's put this into project level changelog, as this is core lib level update.

[wu-sheng]

All CIs passed without error. @wankai123 Is this good to you? Any more tests or validation you want to do.