从依赖模块装配Bean：配置项目Bean在客户端不生效求助

Hey there! Let’s work through why your client project isn’t picking up the beans from your configuration dependency. I’ve run into this exact issue before, so here are the key things to check:

• Ensure your configuration class is being scanned by Spring
  By default, Spring only scans packages within the client project’s root package (and subpackages). If your configuration project’s beans live in a separate package, you need to explicitly tell Spring to look there. You can do this in two ways:

  1. Add the configuration package to your client’s component scan:

     @SpringBootApplication(scanBasePackages = {"com.your.client.root", "com.your.config.package"})
     public class ClientApplication {
         public static void main(String[] args) {
             SpringApplication.run(ClientApplication.class, args);
         }
     }
     

  2. Directly import the configuration class in your client’s main configuration:

     @SpringBootApplication
     @Import(YourConfigClass.class)
     public class ClientApplication {
         // ...
     }
     

• Verify your configuration class has the correct annotations
  Double-check that your configuration class is marked with @Configuration, and each bean method has the @Bean annotation. Also, make sure bean methods are public (while Spring supports non-public methods, using public avoids unexpected issues):

  @Configuration
  public class YourConfigClass {
      @Bean
      public YourBean yourBean() {
          return new YourBean();
      }
  }
  

• Check your Maven dependency scope
  Ensure the configuration project dependency in your client’s pom.xml uses the compile scope (this is the default, but it’s easy to accidentally set it to test or provided, which would make the beans unavailable at runtime):

  <dependency>
      <groupId>com.your.group</groupId>
      <artifactId>your-config-project</artifactId>
      <version>1.0.0</version>
      <!-- Make sure scope is compile (or omit it, since compile is default) -->
      <scope>compile</scope>
  </dependency>
  

• Confirm the dependency is actually included in your client’s build
  Run mvn dependency:tree in your client project’s root directory. Look for your configuration project’s artifact to ensure it’s listed and there are no exclusion rules preventing it from being included.

• Use Spring Boot’s auto-configuration (if applicable)
  If you’re using Spring Boot, you can turn your configuration project into an auto-configurable starter. Create a file named META-INF/spring/org.springframework.boot.autoconfigure.AutoConfiguration.imports in your configuration project, and add the fully qualified name of your configuration class inside it:

  com.your.config.package.YourConfigClass
  

  This way, any client project that adds your dependency will automatically load the beans without needing manual scanning or imports.

Start with the first two checks—they’re the most common culprits. If those don’t fix it, move on to verifying your Maven setup and auto-configuration.

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