<subscribe>subscribe@</subscribe>
      <unsubscribe>unsubscribe@</unsubscribe>
      <post>post@</post>
      <archive>mail-archive</archive>
      <otherArchives>
        <otherArchive>other-archive</otherArchive>
      </otherArchives>
    </mailingList>
  </mailingLists>

  <prerequisites>
    <maven>2.0.1</maven>
  </prerequisites>

  <scm>
    <url>https://project.url/trunk</url>

  <version>0.1</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-3904</name>
  <description>
    Test that properties which refer to build directories which in turn refer to other build directories are
    properly interpolated.
  </description>

  <properties>
    <!-- These are the properties of interest -->
    <dir0>${project.build.outputDirectory}/dir0</dir0>

  <artifactId>test2</artifactId>
  <version>0.1</version>

  <name>Maven Integration Test :: MNG-4000</name>
  <description>
    Test that plugin executions without id are not lost among other plugin executions.
  </description>

  <build>
    <!-- NOTE: This test uses plugin management for the IT plugin. -->
    <pluginManagement>
      <plugins>
        <plugin>

      <subscribe>subscribe@</subscribe>
      <unsubscribe>unsubscribe@</unsubscribe>
      <post>post@</post>
      <archive>mail-archive</archive>
      <otherArchives>
        <otherArchive>other-archive</otherArchive>
      </otherArchives>
    </mailingList>
  </mailingLists>

  <prerequisites>
    <maven>2.0.1</maven>
  </prerequisites>

  <scm>
    <url>https://project.url/trunk</url>

    builds, dependency management, documentation creation, site
    publication, and distribution publication are all controlled from
    the declarative file. Maven can be extended by plugins to utilise a
    number of other development tools for reporting or the build
    process.
  </description>
  <url>http://maven.apache.org/</url>
  <inceptionYear>2001</inceptionYear>
  <properties>
    <classWorldsVersion>1.3</classWorldsVersion>

    An empty artifact that Guava depends on to signal that it is providing
    ListenableFuture -- but is also available in a second "version" that
    contains com.google.common.util.concurrent.ListenableFuture class, without
    any other Guava classes. The idea is:

    - If users want only ListenableFuture, they depend on listenablefuture-1.0.

    - If users want all of Guava, they depend on guava, which, as of Guava
    27.0, depends on

        <artifactId>maven-it-plugin-a</artifactId>
        <version>1.0-SNAPSHOT</version>
        <dependencies>
          <!-- NOTE: That's exactly the same dependency as for the other plugin. -->
          <dependency>
            <groupId>org.apache.maven.its.mng3838</groupId>
            <artifactId>dep</artifactId>
            <version>123</version>
          </dependency>
        </dependencies>

under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.mng4283</groupId>
  <artifactId>parent</artifactId>
  <version>0.1</version>
  <!-- NOTE: Any packaging other than "pom" must be rejected for a parent POM -->
  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-4283</name>
  <description>
    Test that the model builder fails when a parent POM has not "pom" packaging.

  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-4053</name>
  <description>
    Verify that attributes in plugin configuration elements are not erroneously duplicated to other elements when
    plugin management is used.
  </description>

  <build>
    <!-- NOTE: This test used plugin management for the IT plugin -->
    <pluginManagement>
      <plugins>
        <plugin>

  <artifactId>test1</artifactId>
  <version>0.1</version>

  <name>Maven Integration Test :: MNG-4000</name>
  <description>
    Test that plugin executions without id are not lost among other plugin executions.
  </description>

  <build>
    <!-- NOTE: This test does not use plugin management for the IT plugin. -->
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>