type=pom类型依赖的POM是否可包含构建步骤？

Absolutely! A POM that's added as a <type>pom</type> dependency (often used for aggregating dependencies via a "starter" or BOM pattern) can include build configurations—like resource copying with the Maven Resources Plugin, plugin configurations, or other build steps—though there are important details to get right for these configurations to take effect in your project.

Let’s break down how this works:

1. Key distinction: Pom dependency vs. Parent Pom #

First, it’s critical to separate two ways of using a POM:

• When you reference a POM as a dependency (with <type>pom</type>), its <build> section is not automatically inherited by your project. This is different from using a POM as a parent (via the <parent> tag), where build configurations are automatically merged into your project’s build.

2. Using <pluginManagement> to share build configurations #

To make build steps from your referenced POM available to your project, define them in the <pluginManagement> section of the dependency POM. This section acts as a centralized place to declare plugin versions and configurations that other projects can adopt without repeating code.

Example: Configuring resource copying in the dependency POM #

Here’s what your mysql-starter POM might look like with a Resources Plugin configuration in <pluginManagement>:

<project>
  <groupId>com.mycompany</groupId>
  <artifactId>mysql-starter</artifactId>
  <version>1.0</version>
  <packaging>pom</packaging>

  <pluginManagement>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-resources-plugin</artifactId>
        <version>3.3.1</version>
        <executions>
          <execution>
            <id>copy-custom-resources</id>
            <phase>process-resources</phase>
            <goals>
              <goal>copy-resources</goal>
            </goals>
            <configuration>
              <outputDirectory>${project.build.outputDirectory}/config</outputDirectory>
              <resources>
                <resource>
                  <directory>${project.basedir}/src/main/custom-resources</directory>
                  <filtering>true</filtering>
                </resource>
              </resources>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </pluginManagement>

  <!-- Your aggregated dependencies go here -->
  <dependencies>
    <dependency>
      <groupId>mysql</groupId>
      <artifactId>mysql-connector-java</artifactId>
      <version>8.0.33</version>
    </dependency>
  </dependencies>
</project>

Using the configuration in your project #

To activate this build step in your project that references mysql-starter, you just need to declare the plugin in your project’s <build> section—no need to repeat the entire configuration:

<project>
  <!-- ... other project config ... -->
  <dependencies>
    <dependency>
      <groupId>com.mycompany</groupId>
      <artifactId>mysql-starter</artifactId>
      <version>1.0</version>
      <type>pom</type>
      <scope>import</scope> <!-- Use import scope if it's a BOM; omit for regular pom dependencies -->
    </dependency>
  </dependencies>

  <build>
    <plugins>
      <!-- This inherits the configuration from mysql-starter's pluginManagement -->
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-resources-plugin</artifactId>
      </plugin>
    </plugins>
  </build>
</project>

3. What happens if you put build steps directly in <build>? #

If you define plugins directly in the <build> section (not <pluginManagement>) of your dependency POM, those steps won’t automatically run in your referencing project. Your project would need to explicitly declare and configure the plugin itself—defeating the purpose of centralizing the configuration in the starter POM.

Wrap-up #

So to answer your question clearly: Yes, the referenced POM can include build steps, but you’ll want to use <pluginManagement> to define them so referencing projects can easily adopt the configuration. If you’re using the POM as a parent instead of a dependency, the <build> configurations will be inherited automatically.

内容的提问来源于stack exchange，提问作者Darius X.