<artifactId>parent</artifactId>
  <version>0.1</version>
  <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

  </parent>

  <groupId>org.apache.maven.its.mng4415</groupId>
  <artifactId>test</artifactId>
  <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

  <artifactId>parent</artifactId>
  <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>

  <groupId>org.apache.maven.its.mng4416</groupId>
  <artifactId>test</artifactId>
  <version>0.1</version>

  <name>Maven Integration Test :: MNG-4416</name>
  <description>
    Test that merging of plugins during profile injection follows these rules regarding ordering:
     model:   X ->      A -> B ->      D -> E
     profile:      Y -> A ->      C -> D ->      F
     result:  X -> Y -> A -> B -> C -> D -> E -> F

  </description>

  <build>
    <plugins>
      <!-- NOTE: It's essential part of this test variant to redefine the test plugin again, i.e. trigger plugin merging -->
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-log-file</artifactId>
        <version>2.1-SNAPSHOT</version>
      </plugin>
    </plugins>
  </build>

    <artifactId>parent</artifactId>
    <version>0.1</version>
  </parent>

  <artifactId>child</artifactId>

  <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/>

  <repositories>

    <artifactId>parent-2</artifactId>
    <version>0.1</version>
  </parent>

  <artifactId>child-2</artifactId>

  <name>Maven Integration Test :: MNG-3937</name>
  <description>
    Test that during inheritance/merging of a plugin execution the goals specified by child and parent are properly
    ordered.
  </description>

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

					<controlDir>${project.build.directory}/generated-packaging/deb/scripts</controlDir>
					<!--
					<signPackage>${deb.sign}</signPackage>
					<keyring>${gpg.keyring}</keyring>
					key>${gpg.key}</key>
					<passphrase>${gpg.passphrase}</passphrase>
					<signMethod>${deb.sign.method}</signMethod>
					-->
					<dataSet>
						<!-- Add app directory -->
						<data>

    <artifactId>parent-1</artifactId>
    <version>0.1</version>
  </parent>

  <artifactId>child-1</artifactId>

  <name>Maven Integration Test :: MNG-3937</name>
  <description>
    Test that during inheritance/merging of a plugin execution the goals specified by child and parent are properly
    ordered.
  </description>

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

  <artifactId>parent-2</artifactId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-3937</name>
  <description>
    Test that during inheritance/merging of a plugin execution the goals specified by child and parent are properly
    ordered.
  </description>

  <build>
    <!-- This project uses plugin management for the test plugin -->
    <pluginManagement>