向非当前模块为父的Maven子模块传属性及多模块配置疑问

Let's break down your two questions with practical, actionable solutions tailored to your project setup:

1. How to pass properties to Maven submodules that don't use the current module as their parent? #

Maven's native property inheritance only works directly between parent-child modules, but there are clean, production-ready ways to share properties across non-parent-child modules:

Option 1: Use a BOM (Bill of Materials) Module #

This is the most recommended approach for sharing properties and dependency versions across unrelated modules. Here's how to implement it:

• You can repurpose your all-services-parent as the BOM, or create a dedicated BOM module. Define all your shared properties in its <properties> section:

  <groupId>your.group.id</groupId>
  <artifactId>project-bom</artifactId>
  <version>1.0.0-SNAPSHOT</version>
  <packaging>pom</packaging>
  
  <properties>
    <spring.boot.version>2.7.15</spring.boot.version>
    <commons.lang3.version>3.12.0</commons.lang3.version>
    <!-- Add all shared properties here -->
  </properties>
  

• In any module that needs access to these properties (even if it's not a child of the BOM/parent module), import the BOM in its <dependencyManagement> section:

  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>your.group.id</groupId>
        <artifactId>project-bom</artifactId>
        <version>1.0.0-SNAPSHOT</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
    </dependencies>
  </dependencyManagement>
  

  Now you can reference the shared properties (like ${spring.boot.version}) directly in the module's pom, no parent-child relationship required.

Option 2: Load Properties from an External File #

If you prefer a file-based approach, use the maven-properties-plugin to load shared properties from a common file (e.g., stored in commons-lib/src/main/resources/shared.properties):

• Add this plugin configuration to any module that needs the properties:

  <build>
    <plugins>
      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>properties-maven-plugin</artifactId>
        <version>1.1.0</version>
        <executions>
          <execution>
            <phase>initialize</phase>
            <goals>
              <goal>read-project-properties</goal>
            </goals>
            <configuration>
              <files>
                <file>../commons-lib/src/main/resources/shared.properties</file>
              </files>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>
  

  Note: This requires consistent file paths across builds, which can be tricky for standalone module releases—stick with the BOM approach if possible.

2. If the first four projects are submodules of the fifth parent project, do they need specific configurations? #

Yes, they require minimal but essential configurations to work properly as submodules, plus extra tweaks for standalone releases:

Required Configurations for Submodules #

1. Parent POM Reference: Each submodule's pom.xml must declare the parent module in the <parent> section:

   <parent>
     <groupId>your.group.id</groupId>
     <artifactId>all-services-parent</artifactId>
     <version>1.0.0-SNAPSHOT</version>
     <!-- Use relativePath only for local builds; remove it for standalone releases to pull from your Maven repo -->
     <relativePath>../all-services-parent/pom.xml</relativePath>
   </parent>
   

   This lets the submodule inherit properties, dependency management, and plugin configurations from the parent.

2. Unique Artifact ID: Each submodule must define its own <artifactId> (since the parent's groupId and version are inherited). For example:

   <artifactId>user-service</artifactId>
   

3. Parent Module Module Listing: The all-services-parent must list all submodules in its <modules> section to trigger multi-module builds:

   <modules>
     <module>../commons-lib</module>
     <module>../user-service</module>
     <module>../composite-service</module>
     <module>../frontend-service</module>
   </modules>
   

Standalone Release Considerations #

Since your submodules (except commons-lib) need to be released independently, ensure their POMs are self-sufficient:

• Remove the <relativePath> from the <parent> section when releasing, so Maven pulls the parent POM from your Maven repository instead of relying on a local file.
• If you used the BOM approach from question 1, your submodules will already have access to shared properties even when built standalone.

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