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

m := map[int]int{a: 1, a: 2}  // m may be {2: 1} or {2: 2}: evaluation order between the two map assignments is not specified
n := map[int]int{a: f()}      // n may be {2: 3} or {3: 3}: evaluation order between the key and the value is not specified
</pre>

<p>
At package level, initialization dependencies override the left-to-right rule

represents the bitwise and instruction,
<code>AND</code> (without the leading <code>A</code>),
and is written in assembly source as <code>AND</code>.
The enumeration is mostly in alphabetical order.
(The architecture-independent <code>AXXX</code>, defined in the
<code>cmd/internal/obj</code> package,
represents an invalid instruction).
The sequence of the <code>A</code> names has nothing to do with the actual

            resource to allow Maven to merge changes to this resource that take
            place during the execution of a plugin. This field must be managed
            by the generated parser and formatter classes in order to allow it
            to survive model interpolation.
          </description>
          <type>String</type>
        </field>
      </fields>
      <codeSegments>
        <codeSegment>

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