</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see https://goo.gl/pRV3Yn for details.

    The summary is that it ignores one file in favor of the other.

  <!-- NOTE: The upper-case packaging name is intentional and triggers a special mode in the EmptyLifecycleExecutor -->
  <packaging>JAR</packaging>

  <name>Maven Integration Test :: MNG-4341</name>
  <description>
    Test that plugins bound to the same phase get executed in POM order even if one of the plugins participates
    in the default lifecycle bindings for the project's packaging.
  </description>

  <build>
    <plugins>
      <plugin>

</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see https://goo.gl/pRV3Yn for details.

    The summary is that it ignores one file in favor of the other.

</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see https://goo.gl/pRV3Yn for details.

    The summary is that it ignores one file in favor of the other.

</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see https://goo.gl/pRV3Yn for details.

    The summary is that it ignores one file in favor of the other.

            path. As the name suggests, this is similar to requiresDependencyResolution and supports the same values.
            The important difference is this will not resolve the files for the dependencies, i.e. the artifacts
            associated with a Maven project can lack a file. As such, this annotation is meant for Mojos that only

  <artifactId>
    parent
  </artifactId>
  <version>
    1.0
  </version>
  <packaging>
    pom
  </packaging>

  <name>Maven Integration Test :: MNG-4070</name>
  <description>
    Test that whitespace around artifact coordinates does not change artifact identity.
  </description>

  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.mng3586</groupId>
  <artifactId>test2</artifactId>
  <version>1.0</version>

  <name>Maven Integration Test :: MNG-3586</name>
  <description>
    Test that plugin dependencies with scope system are part of the plugin class realm.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>

  <groupId>org.apache.maven.its.mng4193</groupId>
  <artifactId>test</artifactId>
  <version>0.1</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-4193</name>
  <description>
    Test that multiple artifact repository declarations with the same id cause a validation error.
  </description>

  <repositories>
    <repository>
      <id>one</id>
      <url>https://repo1.maven.org/maven2</url>

  </parent>

  <artifactId>subproject</artifactId>
  <version>1.0</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-4070 :: Child</name>
  <description>
    Test that whitespace around artifact coordinates does not change artifact identity.
  </description>

  <dependencies>
    <dependency>
      <!-- NOTE: The ugly formatting is essential part of this test! -->