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

          <association>
            <type>Dependency</type>
            <multiplicity>*</multiplicity>
          </association>
          <description>
            A set of dependencies which the plugin requires in order to function. This enables the plugin to function
            independently of its POM (or at least to declare the libraries it needs to run).
          </description>
        </field>
      </fields>
      <codeSegments>

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

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

  <name>Maven Integration Test :: MNG-3887</name>
  <description>
    Test that multiple plugin executions bound to the same phase are executed in the order given by the POM.
  </description>

  <build>
    <!-- This project uses plugin management for the test plugin -->
    <pluginManagement>
      <plugins>
        <plugin>

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

  <name>Maven Integration Test :: MNG-4003</name>
  <description>
    Verify that dependencies survive the project construction in the POM order.
  </description>

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

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

  <name>Maven Integration Test :: MNG-4003</name>
  <description>
    Verify that dependencies survive the project construction in the POM order.
  </description>

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

      | of Guice has any impact on what we may categorize as a standard JSR-330 based Tesla/Maven plugin.

        <exportedPackage>com.google.inject.*</exportedPackage>
        <exportedPackage>com.google.inject.binder.*</exportedPackage>
        <exportedPackage>com.google.inject.matcher.*</exportedPackage>
        <exportedPackage>com.google.inject.name.*</exportedPackage>
        <exportedPackage>com.google.inject.spi.*</exportedPackage>

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

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