Replace deprecated MapAccessor from Spring 7.0#24501
Conversation
it is only a matter of changing the package name Signed-off-by: Aurélien Pupier <apupier@ibm.com>
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
gnodet
left a comment
There was a problem hiding this comment.
Clean one-liner — thank you, Aurélien!
The import change is correct. org.springframework.context.expression.MapAccessor is @Deprecated(since = "7.0", forRemoval = true) per Spring Framework #35537, and Camel is on Spring 7.0.8, making this directly relevant. The replacement class org.springframework.expression.spel.support.MapAccessor is the official migration path — the deprecated class literally extends the new one, so the API is identical. This is the only file in the codebase using the old import.
Checklist:
- ✅ Tests — no behavioral change; existing SpEL tests cover this code path
- ✅ Docs/upgrade guide — not needed (internal import change, no user-facing impact)
- ✅ Completeness — only usage of the deprecated import in the codebase
- ✅ No security, API, or backward-compat concerns
No issues found.
Note: This PR is currently in draft status — posting as an early review.
This review does not replace specialized AI review tools or static analysis.
Reviewed with Claude Code on behalf of @gnodet. This review was generated by an AI agent and may contain inaccuracies; please verify all suggestions before applying.
|
🧪 CI tested the following changed modules:
🔬 Scalpel shadow comparison — Scalpel: 233 tested, 29 compile-only — current: 233 all testedMaveniverse Scalpel detected 262 affected modules (current approach: 233).
|
it is only a matter of changing the package name
Description
Target
mainbranch)Tracking
Apache Camel coding standards and style
mvn clean install -DskipTestslocally from root folder and I have committed all auto-generated changes.AI-assisted contributions
Co-authored-bytrailers) and the PR description identifies the AI tool used.