When @ComponentScan Skipped My Package
A small package move that broke more than I thought
This happened over a year ago. I thought my setup was fine, clean project structure, services split into their own package, and @ComponentScan
set up. But for a good chunk of time, my app acted like my services didn’t exist. They weren’t picked up, weren’t injected, and Spring did complain but I skipped past the error in the logs and thought it actually had started just fine.
I didn’t plan to write about it at the time, but the more I looked at it, the more I realized how easy it is to mess this up without realizing.
Keep reading with a 7-day free trial
Subscribe to Alexander Obregon's Substack to keep reading this post and get 7 days of free access to the full post archives.