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

  <profiles>
    <profile>
      <id>local-profile</id>
      <properties>
        <local-profile-prop>local-profile-prop-value</local-profile-prop>
      </properties>
    </profile>
  </profiles>

  <activeProfiles>
    <activeProfile>local-profile</activeProfile>
  </activeProfiles>

  <description>
    Test that profiles are injected in declaration order, with the last profile being the most dominant.
  </description>

  <profiles>
    <!-- NOTE: Using intentionally more than two profiles to prevent random test success -->
    <profile>
      <id>pom-a</id>
      <properties>
        <pomProperty>a</pomProperty>
      </properties>
    </profile>
    <profile>
      <id>pom-b</id>
      <properties>

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

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

-->

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

     | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
     | This will make it more intuitive to understand what the set of introduced profiles is attempting
     | to accomplish, particularly when you only have a list of profile id's for debug.
     |
     | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
    <profile>
      <id>jdk-1.4</id>

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

  <profiles>
    <profile>
      <id>maven-core-it</id>
      <activation>
        <activeByDefault>true</activeByDefault>
      </activation>
      <dependencies>
        <dependency>

        </executions>
      </plugin>
    </plugins>
  </build>

  <profiles>
    <profile>
      <!-- an active but empty profile to ensure profile injection does not interfere with plugin configuration -->
      <id>child</id>
      <activation>
        <activeByDefault>true</activeByDefault>
      </activation>
    </profile>
  </profiles>

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