import javax.inject.Inject;
import javax.inject.Named;
import javax.inject.Singleton;

/**
 * {@code war} packaging plugins bindings provider for {@code default} lifecycle.
 */
@Named("war")
@Singleton
public final class WarLifecycleMappingProvider extends AbstractLifecycleMappingProvider {
    // START SNIPPET: war
    private static final String[] BINDINGS = {
        "process-resources",

        MavenProject lib = session.getProjects().get(1);
        MavenProject war = session.getProjects().get(2);

        assertNull(war.getArtifactMap()
                .get("org.apache.maven.its.mng6300:mng6300-lib")
                .getFile());

        lib.getArtifact().setFile(new File("lib.jar"));

        resolver.resolveProjectDependencies(
                war, scopesToCollect, scopesToResolve, session, aggregating, reactorArtifacts);

Hug war eines der ersten Frameworks, welches die Deklaration von API-Parametertypen mithilfe von Python-Typhinweisen implementierte. Das war eine großartige Idee, die andere Tools dazu inspirierte, dasselbe zu tun.

Es verwendete benutzerdefinierte Typen in seinen Deklarationen anstelle von Standard-Python-Typen, es war aber dennoch ein großer Fortschritt.

    <artifactId>test</artifactId>
    <version>1.0</version>
  </parent>
  <artifactId>mng6300-war</artifactId>
  <packaging>war</packaging>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-war-plugin</artifactId>
        <configuration>
          <failOnMissingWebXml>false</failOnMissingWebXml>
        </configuration>

 *
 * <h2>Standard Packaging Types</h2>
 * <ul>
 *     <li>{@code jar}: Packages the project as a Java Archive (JAR) file.</li>
 *     <li>{@code war}: Packages the project as a Web Application Archive (WAR) file.</li>
 *     <li>{@code pom}: Indicates that the project does not produce a deployable artifact but is used for dependency management or as an aggregator.</li>

  <groupId>org.apache.maven.its.mng6300</groupId>
  <artifactId>test</artifactId>
  <version>1.0</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-6300</name>
  <description>
    Check that war packages the jar instead of a directory
  </description>

  <reporting>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-javadoc-plugin</artifactId>

    <!-- These packages are duplicated in core and war, don't require a package-info.java in each place -->
    <suppress checks="JavadocPackage"
              files=".*[/\\]platforms[/\\]jvm[/\\]war[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]api[/\\]plugins[/\\][^/\\]+"/>
    <suppress checks="JavadocPackage"

          "instrumentation-agent-services",
          "logging",
          "messaging",
          "plugins-java-base",
          "problems",
          "problems-api",
          "resources-gcs",
          "war"
        ],
        "parallelizationMethod": {
          "name": "TestDistribution"
        }
      },
      {
        "subprojects": [
          "build-cache-http",
          "build-events",

    }

    /** The file extension for class files. */
    protected static final String CLASS_SUFFIX = ".class";

    /** The file extension for WAR files. */
    protected static final String WAR_FILE_EXTENSION = ".war";

    /** The entry prefix for class files inside a WAR file. */
    protected static final String WEB_INF_CLASSES_PATH = "WEB-INF/classes/";

    /**
     * Processes the directory under the root directory.

%{snippet|id=maven-plugin|file=${project.basedir}/src/main/java/org/apache/maven/lifecycle/providers/packaging/MavenPluginLifecycleMappingProvider.java}

* Plugin bindings for <<<war>>> packaging

%{snippet|id=war|file=${project.basedir}/src/main/java/org/apache/maven/lifecycle/providers/packaging/WarLifecycleMappingProvider.java}

* Plugin bindings for <<<ear>>> packaging