@SpringBootApplication包扫描失效：多模块Maven项目自动装配异常求助

Hey there, let's tackle this autowiring issue you're facing with your Spring Boot multi-module app. I've run into similar headaches before, so here's what you can check and fix step by step:

1. 确认子模块的Maven依赖是否正确引入 #

First off, make sure your main module's pom.xml has properly added dependencies for each sub-module. If the sub-module isn't in your main module's classpath, Spring can't possibly scan its beans. Here's what a valid dependency entry should look like:

<dependency>
    <groupId>com.ams</groupId>
    <artifactId>your-submodule-artifactId</artifactId>
    <version>your-module-version</version>
</dependency>

After updating the pom, run mvn clean install on the parent project (if you have one) or on both the sub-module and main module to ensure everything is built and linked correctly.

2. 验证子模块中的Bean是否标注了正确的Spring注解 #

Spring only manages classes marked with its stereotype annotations. Double-check that:

• Repository classes are annotated with @Repository
• Service classes have @Service
• General components use @Component
• JPA entity classes are marked with @Entity (if you're using JPA)
• Configuration classes have @Configuration

If a class lacks these annotations, Spring won't register it as a bean, leading to autowiring failures.

3. 显式指定组件扫描范围（如果默认扫描未生效） #

Your main @SpringBootApplication class is in com.ams.web, which should automatically scan all sub-packages under com.ams.web (like com.ams.web.service, com.ams.web.repository). But sometimes module isolation or classloader quirks can break this. To fix it, explicitly set the scan base packages:

@SpringBootApplication(scanBasePackages = "com.ams.web")
public class AmsWebApplication {
    public static void main(String[] args) {
        SpringApplication.run(AmsWebApplication.class, args);
    }
}

If you have sub-modules under other related packages (like com.ams.common), you can pass multiple packages as an array:

@SpringBootApplication(scanBasePackages = {"com.ams.web", "com.ams.common"})

Alternatively, you can use @ComponentScan alongside @SpringBootApplication for the same effect.

4. 检查子模块的包结构是否完全匹配 #

It sounds obvious, but double-check that your sub-module classes are actually in the correct package paths. For example, make sure your service class is in com.ams.web.service and not a typo like com.ams.service or com.ams.web.services—even a small misspelling will prevent Spring from finding it.

5. 开启调试日志诊断扫描问题 #

If you're still stuck, turn on Spring's component scan debug logs to see exactly which beans are being picked up. Add this line to your application.properties or application.yml:

logging.level.org.springframework.context.annotation=DEBUG

When you start the app, the logs will show every package Spring scans and every bean it registers. This can help you spot if your sub-module's packages are being skipped entirely.

内容的提问来源于stack exchange，提问作者Guru