在POM中配置<packaging>war</packaging>后，是否需显式添加War插件？

Great question! Let's break this down clearly for you:

Short Answer #

No, you don't need to manually add the War Plugin configuration block for most basic web projects.

Why That's the Case #

Maven uses built-in lifecycle bindings that automatically map plugins to specific packaging types. When you set <packaging>war</packaging> in your pom.xml, Maven will automatically pull in the maven-war-plugin with its default settings. This means running mvn package will generate a valid .war file in the ./target directory without any extra plugin configuration.

The default behavior covers all standard needs for simple web projects:

• Packages compiled classes into WEB-INF/classes
• Includes all project dependencies in WEB-INF/lib
• Uses src/main/webapp as the default web content root
• Names the war file [artifactId]-[version].war (matching your pom's artifact ID and version)

When You Do Need to Add Plugin Configuration #

You only need to manually configure the maven-war-plugin if you want to customize the packaging behavior. Common scenarios where this is necessary include:

• Changing the final name of the war file (e.g., renaming my-app-1.0.war to my-production-app.war)
• Excluding specific files/directories from the war package (like test configs or unused resources)
• Specifying a non-standard location for web.xml (e.g., if you're using annotation-based config and don't have a default WEB-INF/web.xml)
• Controlling which dependencies are included or excluded from WEB-INF/lib
• Adding resource filtering for web content files

Example of Custom War Plugin Configuration #

If you wanted to rename your war and exclude a test properties file, your plugin config would look like this:

<build>
  <plugins>
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-war-plugin</artifactId>
      <version>3.3.2</version> <!-- Specifying a version ensures consistency across environments -->
      <configuration>
        <finalName>my-production-webapp</finalName>
        <excludes>
          <exclude>**/test-config.properties</exclude>
        </excludes>
      </configuration>
    </plugin>
  </plugins>
</build>

Final Takeaway #

Stick with just <packaging>war</packaging> if your project follows Maven's standard web project structure and doesn't need custom packaging rules. Only add the plugin configuration when you need to tweak how the war is built to fit your project's specific needs.

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