多模块Java项目构建自动化从Ant迁移至Maven，需调用build.xml生成EAR

Hey there! Let's walk through how to migrate your multi-module Java project from Ant to Maven—while still leveraging your existing build.xml logic—and end up with an EAR package. I’ve done this exact migration a few times, so here’s a practical, step-by-step approach:

Start by creating a parent Maven project (packaging type pom) as the root. This will act as a central hub for managing all your submodules, dependencies, and build config. Your final directory structure should look something like this:

your-root-project/
├── pom.xml (parent POM)
├── ejb-module/
│   └── pom.xml
├── web-module/
│   └── pom.xml
└── ear-module/
    └── pom.xml

• The parent POM holds shared settings.
• Submodules correspond to your existing components (EJB, web app, etc.).
• The EAR module will package all other modules into the final EAR file.

In the parent pom.xml, declare your submodules, set common properties, and manage dependencies/plugins to keep consistency across all modules. Example snippet:

<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.yourcompany</groupId>
  <artifactId>your-root-project</artifactId>
  <version>1.0.0</version>
  <packaging>pom</packaging>

  <!-- List all your submodules here -->
  <modules>
    <module>ejb-module</module>
    <module>web-module</module>
    <module>ear-module</module>
  </modules>

  <!-- Shared build properties -->
  <properties>
    <maven.compiler.source>11</maven.compiler.source>
    <maven.compiler.target>11</maven.compiler.target>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
  </properties>

  <!-- Manage dependency versions centrally to avoid duplication -->
  <dependencyManagement>
    <!-- Add entries for your project dependencies here -->
  </dependencyManagement>
</project>

For each submodule (EJB, web app), create a pom.xml with the correct packaging type:

• EJB module: Use <packaging>ejb</packaging>
• Web module: Use <packaging>war</packaging>

Start by migrating your dependencies to Maven first—you can use the dependency:analyze plugin later to catch gaps. Don’t worry about full build logic yet; we’ll hook up the Ant tasks next.

The EAR module’s POM is responsible for packaging all your submodules into the final EAR. Use the maven-ear-plugin to define which modules to include and configure details like context roots. Example:

<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <parent>
    <groupId>com.yourcompany</groupId>
    <artifactId>your-root-project</artifactId>
    <version>1.0.0</version>
  </parent>
  <artifactId>ear-module</artifactId>
  <packaging>ear</packaging>

  <!-- Declare dependencies on your submodules -->
  <dependencies>
    <dependency>
      <groupId>com.yourcompany</groupId>
      <artifactId>ejb-module</artifactId>
      <version>1.0.0</version>
      <type>ejb</type>
    </dependency>
    <dependency>
      <groupId>com.yourcompany</groupId>
      <artifactId>web-module</artifactId>
      <version>1.0.0</version>
      <type>war</type>
    </dependency>
  </dependencies>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-ear-plugin</artifactId>
        <version>3.3.0</version>
        <configuration>
          <modules>
            <ejbModule>
              <groupId>com.yourcompany</groupId>
              <artifactId>ejb-module</artifactId>
            </ejbModule>
            <webModule>
              <groupId>com.yourcompany</groupId>
              <artifactId>web-module</artifactId>
              <contextRoot>/your-web-app</contextRoot>
            </webModule>
          </modules>
          <!-- Enable automatic generation of application.xml if you don't have a custom one -->
          <generateApplicationXml>true</generateApplicationXml>
        </configuration>
      </plugin>
    </plugins>
  </build>
</project>

To call your existing Ant tasks from Maven, use the maven-antrun-plugin. You can bind this plugin to specific Maven phases (like compile or generate-sources) to run Ant targets at the right point in the build.

Example: Run Ant Tasks in the EJB Module #

Add this to your ejb-module/pom.xml under the <build> section:

<plugins>
  <plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-antrun-plugin</artifactId>
    <version>3.1.0</version>
    <executions>
      <execution>
        <id>execute-ant-custom-tasks</id>
        <!-- Bind to a Maven phase that makes sense for your task -->
        <phase>compile</phase>
        <goals>
          <goal>run</goal>
        </goals>
        <configuration>
          <tasks>
            <!-- Import your existing build.xml and run a specific target -->
            <ant antfile="${project.basedir}/build.xml">
              <target name="your-custom-ant-target"/>
            </ant>
            <!-- Optional: Pass Maven properties to Ant -->
            <property name="maven-build-dir" value="${project.build.directory}"/>
          </tasks>
        </configuration>
      </execution>
    </executions>
  </plugin>
</plugins>

Key Tips for Ant Integration: #

• Use Maven’s built-in properties (like ${project.basedir} or ${project.build.directory}) to keep paths portable.
• Choose the correct Maven phase to bind your Ant task—for example, bind source-generation tasks to generate-sources so Maven picks up the output.
• If your Ant task modifies files, aim to output to Maven’s standard directories to keep the build consistent.

Once everything is configured, run this command from the root project directory:

mvn clean install

This will build all modules, execute your Ant tasks where configured, and generate the final EAR file in ear-module/target/.

• If you have conflicting dependencies between Maven and Ant, use the parent POM’s <dependencyManagement> section to override versions.
• Test the EAR deployment to your application server early to catch any packaging issues.
• If your Ant tasks rely on custom environment variables, pass them to Maven using -Dvariable=value when running the build.

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