fix: make shenyu-examples-mcp work normally

[hengyuss]

Fixes: #7032

Make sure that:

• You have read the contribution guidelines.
• You submit test cases (unit or integration tests) that back your changes.
• Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

🟡 Changes recommended

The shared snapshot dependency prevents clean standalone example builds unless the artifact or build/documentation override is provided.

Get a fresh assessment by requesting another Copilot review.

Review details

• Files reviewed: 12/12 changed files
• Comments generated: 1
• Review effort level: Lite

[hengyuss]

Should I revert the version in the shenyu-client parent POM to 2.7.0.3 while allowing shenyu-examples-mcp to use 2.7.2-snapshot separately?
If examples depend on multiple shenyu-clients, issues may arise where upstream services fail to register successfully. So I change ther the version in the shenyu-client parent POM to 2.7.2-snapshot for the fix can apply.
@dengliming

[dengliming]

@hengyuss Thanks for the explanation. I understand the motivation for aligning the client versions to avoid registration issues when multiple shenyu-client versions are involved.

My concern is that changing the shared shenyu.client.java.version to 2.7.2-SNAPSHOT affects all examples, not just shenyu-examples-mcp, and introduces a dependency on an unreleased snapshot version for clean standalone builds. Since the examples README still points to the published 2.7.0.3 artifacts, this could make the repository harder to build for other contributors.

Would it be possible to keep the parent version on the released artifact and apply a more scoped override for shenyu-examples-mcp, or update the related build/documentation together if the whole examples module now requires the snapshot?

[Aias00]

Approved as PMC (Aias00). Coherent fix with regression tests; green CI, mergeable. Reviewed the diff.

[hengyuss]

I think update the related build/documentation is a good choice and I will do it