</plugins>
      </build>
    </profile>
    <profile>
      <id>profile4</id>
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.its.plugins</groupId>
            <artifactId>maven-it-plugin-touch</artifactId>
            <version>2.1</version>
          </plugin>
        </plugins>
      </build>
    </profile>
  </profiles>

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

    </parent>
    <modelVersion>4.0.0</modelVersion>
    <groupId>org.sonatype.nexus</groupId>
    <artifactId>nexus</artifactId>
    <version>1.3.0-SNAPSHOT</version>
    <profiles>
        <profile>
            <id>test</id>
            <build>
                <plugins>
                    <plugin>
                        <groupId>org.codehaus.modello</groupId>

-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.mng4005</groupId>
  <artifactId>b</artifactId>
  <version>0.1</version>
  <packaging>jar</packaging>

  <profiles>
    <profile>
      <id>test</id>
      <dependencies>
        <dependency>
          <groupId>org.apache.maven.its.mng4005</groupId>
          <artifactId>a</artifactId>
          <version>0.1</version>
        </dependency>

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

  <profiles>
    <profile>
      <id>maven-core-it</id>
      <activation>
        <activeByDefault>true</activeByDefault>
      </activation>
      <dependencies>
        <dependency>
          <groupId>org.apache.maven.its</groupId>

              </goals>
              <phase>none</phase>
            </execution>
          </executions>
        </plugin>
      </plugins>
    </pluginManagement>
  </build>

  <profiles>
    <profile>
      <id>reporting</id>
      <reporting>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-javadoc-plugin</artifactId>

          <type>String</type>
          <description>
            The goal name for the Mojo, that users will reference from the command line to execute the Mojo directly,
            or inside a POM in order to provide Mojo-specific configuration.
          </description>
        </field>
        <field>
          <name>description</name>
          <version>1.0.0+</version>
          <type>String</type>

          </plugin>
          <plugin>
            <artifactId>only-active-profile</artifactId>
            <executions>
              <execution>
                <id>Active only ||${project.basedir}||</id>
                <configuration>
                  <plugin-in-active-profile-only>Active only ||${project.basedir}||</plugin-in-active-profile-only>
                </configuration>
              </execution>

          <version>2.1-SNAPSHOT</version>
        </plugin>
      </plugins>
    </pluginManagement>
  </build>

  <profiles>
    <profile>
      <!-- NOTE: This test injects the plugin configuration via a profile -->
      <id>maven-core-it</id>
      <activation>
        <activeByDefault>true</activeByDefault>
      </activation>
      <build>
        <plugins>
          <plugin>

  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-4107</name>
  <description>
    Test that POM interpolation uses the property values from the dominant profile source (POM vs. settings.xml).
    This boils down to the proper order of profile injection and interpolation, i.e.
    interpolate after profiles from all sources are injected.
  </description>

  <properties>