<stringParam>CHILD-1</stringParam>
            <stringParam>CHILD-3</stringParam>
            <stringParam>CHILD-2</stringParam>
            <stringParam>CHILD-4</stringParam>
          </stringParams>
          <listParam combine.children="append">
            <!-- NOTE: These values are deliberately not in alpha order! -->
            <listParam>CHILD-1</listParam>

          <version>2.1-SNAPSHOT</version>
          <inherited>true</inherited>
          <configuration>
            <listParam>
              <!-- NOTE: These values are deliberately not in alpha order! -->
              <listParam>PARENT-1</listParam>
              <listParam>PARENT-3</listParam>
              <listParam>PARENT-2</listParam>
              <listParam>PARENT-4</listParam>
            </listParam>

  <artifactId>test</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-2309</name>
  <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>

  <artifactId>test</artifactId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-3808</name>
  <description>
    Test the reports are executed in the order given in the POM.
  </description>

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

      <version>1.0</version>
      <type>jar</type>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>surefire</groupId>
      <artifactId>surefire-booter</artifactId>
      <version>1.1</version>
      <type>jar</type>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>maven</groupId>
      <artifactId>wagon-api</artifactId>

  <version>0.1-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-1412</name>
  <description>
    Check that dependencies are available in classpath in same order as declared in POM.
  </description>

  <dependencies>
    <!-- model dependencies first, in the order given -->
    <dependency>
      <groupId>org.apache.maven.its.mng1412</groupId>
      <artifactId>a</artifactId>
      <version>0.1</version>
    </dependency>

  <name>Maven Integration Test :: MNG-4102</name>
  <description>
    Verify that the effective value of an inherited property reflects the values of any nested property
    as defined by the child. This boils down to the order of inheritance and (parent) interpolation.
  </description>

  <properties>
    <overridden>PARENT</overridden>
    <!-- Test the effective value of this property in the child when "overridden" is defined by child as well -->

  <packaging>JAR</packaging>

  <name>Maven Integration Test :: MNG-4341</name>
  <description>
    Test that plugins bound to the same phase get executed in POM order even if one of the plugins participates
    in the default lifecycle bindings for the project's packaging.
  </description>

  <build>
    <plugins>
      <plugin>

  <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>
    <!-- collect the effective property values as derived by interpolation -->

            <stringParam>CHILD-1</stringParam>
            <stringParam>CHILD-3</stringParam>
            <stringParam>CHILD-2</stringParam>
            <stringParam>CHILD-4</stringParam>
          </stringParams>
          <listParam combine.children="append">
            <!-- NOTE: These values are deliberately not in alpha order! -->
            <listParam>CHILD-1</listParam>