-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <parent>
    <groupId>org.apache.maven.its.mng3808</groupId>
    <artifactId>test</artifactId>
    <version>0.1</version>
  </parent>
  <artifactId>child</artifactId>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-configuration</artifactId>
        <version>2.1-SNAPSHOT</version>

  <parent>
    <groupId>org.apache.maven.its.mng4034</groupId>
    <artifactId>parent</artifactId>
    <version>1.0-SNAPSHOT</version>
  </parent>

  <groupId>org.apache.maven.its.mng4034</groupId>
  <artifactId>child</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-4034</name>
  <description>
    Verify that dependencies defined in profiles are subject to the dependency management of the parent.

  <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>
        <groupId>org.apache.maven.its.plugins</groupId>

  <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>
        <groupId>org.apache.maven.its.plugins</groupId>

  <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>
      <id>equal-repo-id</id>

<project>
  <modelVersion>4.0.0</modelVersion>

  <!--
  While <licenses> are inherited, they are not aggregated, only the child licenses are used.
  -->

  <parent>
    <groupId>org.apache.maven.its.mng3843</groupId>
    <artifactId>parent-1</artifactId>
    <version>0.1</version>
  </parent>

  <groupId>org.apache.maven.its.mng3843.child</groupId>
  <artifactId>child-2</artifactId>
  <version>0.2</version>

        <!-- NOTE: Use different version than parent -->
        <version>2.0</version>
        <executions>
          <execution>
            <id>child-1</id>
            <phase>child-1</phase>
          </execution>
          <execution>
            <id>child-2</id>
            <phase>child-2</phase>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>

        <executions>
          <execution>
            <!-- NOTE: Explicitly reference "default" id here -->
            <id>default</id>
            <phase>child-default</phase>
          </execution>
          <execution>
            <id>non-default</id>
            <phase>child-non-default</phase>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>

<project>
  <parent>
    <groupId>gid</groupId>
    <artifactId>child-3</artifactId>
    <version>1.0</version>
    <relativePath>child3.xml</relativePath>
  </parent>
  <modelVersion>4.0.0</modelVersion>
  <artifactId>child-2</artifactId>
  <packaging>pom</packaging>

  <description>
    Verify that filter definitions are properly merged.
  </description>

  <build>
    <filters>
      <!-- NOTE: The first filter is deliberately defined by the child as well, so should not be added twice -->
      <filter>src/main/filters/child-a.properties</filter>
      <filter>src/main/filters/parent-c.properties</filter>
      <filter>src/main/filters/parent-b.properties</filter>