spring-projects / spring-projects/spring-framework
Deprecate bean definition overriding
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 60.2k
- Forks
- 38.8k
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 27
Description
As of 6.2, bean definition overriding is made more apparent, and a note in the reference guide discourages users to rely on the feature, see #31288.
In 7.0 we want to deprecate the feature and be more loud if it's still used.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reference guide note described in the issue and review #31288 for the existing treatment of bean definition overriding. Trace where this feature is handled in the Spring Framework and determine the deprecation and more prominent reporting behavior required for 7.0. Done means the feature is deprecated and continued use is clearly reported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100