<artifactId>maven-api</artifactId>
    <version>4.0.0-beta-1-SNAPSHOT</version>
  </parent>

  <artifactId>maven-api-spi</artifactId>
  <name>Maven 4 API :: SPI</name>
  <description>Maven 4 API - Maven SPI.</description>

  <dependencies>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-meta</artifactId>
    </dependency>
    <dependency>

  <artifactId>maven-surefire-plugin</artifactId>
  <version>0.1</version>
  <packaging>maven-plugin</packaging>

  <name>Maven Integration Test Plugin</name>
  <description>
    A test plugin to assist testing of Maven core.
  </description>
  <inceptionYear>2009</inceptionYear>

  <distributionManagement>
    <repository>
      <id>maven-core-it</id>
      <url>file:///${basedir}/repo</url>
    </repository>

  <artifactId>maven-it-plugin</artifactId>
  <version>0.1</version>
  <packaging>maven-plugin</packaging>

  <name>Maven Integration Test Plugin</name>
  <description>
    A test plugin to assist testing of Maven core.
  </description>
  <inceptionYear>2009</inceptionYear>

  <distributionManagement>
    <repository>
      <id>maven-core-it</id>
      <url>file:///${basedir}/repo</url>
    </repository>

  <groupId>commons-logging</groupId>
  <artifactId>commons-logging</artifactId>
  <name>Logging</name>
  <version>1.0.4</version>
  <description>Commons Logging is a thin adapter allowing configurable bridging to other,
    well known logging systems.</description>
  <url>http://jakarta.apache.org/commons/logging/</url>
  <issueManagement>
    <url>http://issues.apache.org/bugzilla/</url>
  </issueManagement>

  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-4415</name>
  <description>
    Test that merging of plugins during inheritance follows these rules regarding ordering:
     parent: X ->      A -> B ->      D -> E
     child:       Y -> A ->      C -> D ->      F
     result: X -> Y -> A -> B -> C -> D -> E -> F
  </description>

  <build>
    <plugins>
      <plugin>

  <version>0.1</version>

  <name>Maven Integration Test :: MNG-4415</name>
  <description>
    Test that merging of plugins during inheritance follows these rules regarding ordering:
     parent: X ->      A -> B ->      D -> E
     child:       Y -> A ->      C -> D ->      F
     result: X -> Y -> A -> B -> C -> D -> E -> F
  </description>

  <build>
    <plugins>
      <plugin>

  <version>0.1</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-3979</name>
  <description>
    Test that during inheritance the merging/joining of subtrees with equal identifier doesn't crash if the parent
    POM has a non-empty element and the child POM has an empty element to join.
  </description>

  <properties>
    <prop0>test</prop0>
  </properties>

  <repositories>
    <repository>

  </parent>
  <modelVersion>4.0.0</modelVersion>
  <artifactId>wagon-provider-api</artifactId>
  <name>Maven Wagon API</name>
  <version>1.0-beta-2</version>
  <description>Maven Wagon API that defines the contract between different Wagon implementations</description>
  <dependencies>
    <dependency>
      <groupId>org.codehaus.plexus</groupId>
      <artifactId>plexus-utils</artifactId>
    </dependency>
  </dependencies>

  </parent>

  <artifactId>hamcrest-core</artifactId>
  <packaging>jar</packaging>
  <name>Hamcrest Core</name>
  <description>
    This is the core API of hamcrest matcher framework to be used by third-party framework providers. This includes the a foundation set of matcher implementations for common operations.
  </description>

  <!-- 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.
  </description>