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

    </default>
  </defaults>
  <classes>
    <class rootElement="true" xml.tagName="remoteResourcesBundle">
      <name>RemoteResourcesBundle</name>
      <version>1.1.0</version>
      <description>Root element of the remote-resources.xml file.</description>
      <fields>
        <field>
          <name>remoteResources</name>
          <version>1.1.0</version>
          <description>

  </defaults>
  <classes>
    <class rootElement="true" xml.tagName="supplementalDataModels" xsd.compositor="sequence">
      <name>SupplementalDataModel</name>
      <version>1.0.0</version>
      <description>Root element of the supplemental-models.xml file.</description>
      <fields>
        <field xml.listStyle="flat">
          <name>supplement</name>
          <version>1.0.0</version>

            <p><b>Note:</b> This will not automagically make a Mojo run when the plugin declaration is added
            to the POM. It merely enables the user to omit the {@code <phase>} element from the
            surrounding {@code <execution>} element.</p>
          </description>
        </field>
        <field>
          <name>executePhase</name>
          <version>1.0.0+</version>
          <type>String</type>

  <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>
    <repository>
      <id>equal-repo-id</id>
      <url>file:///${basedir}/null</url>
      <snapshots/>
      <releases/>

          <artifactId>maven-it-plugin-a</artifactId>
          <version>2.1-SNAPSHOT</version>
          <executions>
            <execution>
              <!-- NOTE: Implicitly reference "default" id here, i.e. omit the <id> element -->
              <phase>parent-default</phase>
            </execution>
            <execution>
              <id>non-default</id>
              <phase>parent-non-default</phase>
            </execution>

        <artifactId>maven-it-plugin-a</artifactId>
        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <!-- NOTE: Implicitly reference "default" id here, i.e. omit the <id> element -->
            <phase>parent-default</phase>
          </execution>
          <execution>
            <id>non-default</id>
            <phase>parent-non-default</phase>
          </execution>
        </executions>

  </description>
  <classes>
    <class rootElement="true" xml.tagName="lifecycles" xsd.compositor="sequence">
      <name>LifecycleConfiguration</name>
      <version>1.0.0</version>
      <description>Root element of the {@code lifecycle.xml} file.</description>
      <fields>
        <field>
          <name>lifecycles</name>
          <version>1.0.0</version>
          <association xml.itemsStyle="flat">

   |-->
  <mirrors>
    <!-- mirror
     | Specifies a repository mirror site to use instead of a given repository. The repository that
     | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
     | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
     |
    <mirror>
      <id>mirrorId</id>
      <mirrorOf>repositoryId</mirrorOf>

specific language governing permissions and limitations
under the License.
-->

<model>
  <groupId>foo</groupId>
  <artifactId>bar</artifactId>
  <name>Babar</name>
  <version>4.5</version>

  <!-- Build element should be inherited from the super model -->