spring-projects / spring-projects/spring-boot
Include information about the scanned packages in failure analysis for NoSuchBeanDefinitionException
Open
Nobody has claimed this yet.
status: blocked
type: enhancement
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
One possible cause of #28832 is that the packages containing the components haven't been scanned. If it's possible to do so, I think it would be useful to include information about the scanned packages in the failure analysis for a NoSuchBeanDefinitionException.
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 locating Spring Boot's failure analysis for NoSuchBeanDefinitionException and inspect how component-scanned packages are represented. The work is done when the failure analysis includes relevant scanned-package information and tests cover the resulting diagnostic output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100