KITFORMA · EDITORIAL ANSWER
Why is a sibling-package Spring service not discovered?
KitForma editorial guide. Default component scanning starts in the application class’s package. A service outside that tree can be valid Java code yet absent from the context.
Step-by-step answer
Default component scanning starts in the application class’s package. A service outside that tree can be valid Java code yet absent from the context.
Place the application class in an intentional root package or configure explicit scan roots. Keep the scan narrow enough to avoid importing unrelated configuration accidentally. For a library module, consider an explicit configuration import instead of scanning the entire classpath.
Run a context test requesting the missing service and inspect duplicate-bean warnings after the change. An annotation does not ensure its package was scanned. Conversely, discovery does not resolve constructor failures: inspect the earliest underlying exception before widening scans again.
Sources and verification
Sources checked:
Scope: This editorial guide is based on the cited sources and tool behavior. A forum question or a query observed for our site does not establish market search volume, low competition, guaranteed rankings or inadequate answers elsewhere.
This editorial answer was prepared by KitForma with AI assistance. It is not presented as a real member question or an independent user review. Check the sources and the result with your own file; report corrections in the discussion.