<groupId>org.apache.maven.its.mng4003</groupId>
      <artifactId>d</artifactId>
      <version>1</version>
    </dependency>
  </dependencies>

  <build>
    <!-- NOTE: The combination with a plugin management section is an essential part of the test -->
    <pluginManagement>
      <plugins>
        <plugin>
          <artifactId>maven-clean-plugin</artifactId>
          <version>2.3</version>
        </plugin>
      </plugins>

      <groupId>org.apache.maven.its.mng4003</groupId>
      <artifactId>d</artifactId>
      <version>1</version>
    </dependency>
  </dependencies>

  <build>
    <!-- NOTE: The combination with a plugin section is an essential part of the test -->
    <plugins>
      <plugin>
        <artifactId>maven-clean-plugin</artifactId>
        <version>2.3</version>
      </plugin>
    </plugins>
  </build>

   | dereferenced during the build process to configure the cactus plugin.
   |
   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
   | section of this document (settings.xml) - will be discussed later. Another way essentially
   | relies on the detection of a property, either matching a particular value for the property,

          <version>1.0.0/1.1.0</version>
          <type>String</type>
          <description>
            Specify the execution strategy: {@code once-per-session}, {@code always}.
          </description>
          <defaultValue>once-per-session</defaultValue>
        </field>
        <field>
          <name>since</name>
          <version>1.0.0+</version>
          <type>String</type>

  </parent>

  <artifactId>child</artifactId>

  <name>Maven Integration Test :: MNG-3916</name>
  <description>
    Test that plugin executions are properly merged during inheritance, even if the child plugin section has no
    version.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-a</artifactId>

  <name>Maven Integration Test :: MNG-2174</name>
  <description>
    Verify that plugin dependencies defined by plugin management of a parent profile are not lost when the
    parent's main plugin management section is also present.
  </description>

  <modules>
    <module>sub</module>
  </modules>

  <build>
    <pluginManagement>
      <plugins>
        <plugin>

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

  <name>Maven Integration Test :: MNG-3916</name>
  <description>
    Test that plugin executions are properly merged during inheritance, even if the child plugin section has no
    version.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-a</artifactId>

  <description>
    Verify that default plugin executions contributed by the packaging are executed before user-defined
    executions from the POM's build section, regardless whether the executions are defined in the regular
    plugins section or the plugin management section.
  </description>

  <build>
    <pluginManagement>
      <plugins>
        <plugin>
          <artifactId>maven-resources-plugin</artifactId>

  <name>Maven Integration Test :: MNG-2174</name>
  <description>
    Verify that plugin dependencies defined by plugin management of a parent profile are not lost when the
    parent's main plugin management section is also present.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-class-loader</artifactId>
        <executions>

            dependencies in this section are not immediately resolved. Instead, when a POM derived
            from this one declares a dependency described by a matching groupId and artifactId, the
            version and other values from this section are used for that dependency if they were not
            already specified.</description>
          <association>