spring-projects / spring-projects/spring-framework
Include @ConditionalOnMissingBean and @ConditionalOnClass from Spring Boot [SPR-11296]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 60.2k
- Forks
- 38.8k
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 27
Description
Oliver Drotbohm opened SPR-11296 and commented
@ConditionalOnMissingBean and @ConditionalOnClass allow to selectively register bean definitions in case a different bean definition is already registered or a type being present on the classpath.
This is really useful to ecosystem projects to be able to pick up user configuration or fall back to defaults otherwise without necessarily creating a dependency on Spring Boot (which might cause a cyclic dependency if boot provides additional defaulting).
Issue Links:
- #15592 Port
@ConditionalOn... from Spring Boot into Spring Core
5 votes, 7 watchers
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 by reading the descriptions of @ConditionalOnMissingBean and @ConditionalOnClass in this issue, then follow the linked issue #15592 about porting @ConditionalOn from Spring Boot into Spring Core. The payload names no implementation files or tests, so the required entry points and completion checks still need to be established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100