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.

Comment From: wilkinsona

39248 made me think about this a little more and I'm pretty sure it's not possible at the moment. @ComponentScan processing is done as an implementation detail of configuration class parsing. To be able to report to the user which packages had been scanned, we'll need a Framework change that makes that information available somewhere. To be really useful, we'd also need information about any filters that were applied as a component may be missing, not because its package was not scanned but because it was filtered out.

@snicoll is there any appetite in the Framework team for capturing this sort of diagnostic information somewhere that we can then use to improve our failure analysis and guidance?

Comment From: snicoll

Sorry for the late reply. We can certainly consider it. Can you please create an issue with more details?

Comment From: wilkinsona

I've opened https://github.com/spring-projects/spring-framework/issues/33022. As you can probably tell by how long it took me, this is more of a nice-to-have than something that we feel we have to do.