<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>
        <groupId>org.apache.maven.its.plugins</groupId>

          </expressions>
        </configuration>
        <executions>
          <execution>
            <id>test</id>
            <phase>validate</phase>
            <goals>
              <goal>eval</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>

            </configuration>
            <executions>
              <execution>
                <id>second</id>
                <phase>validate</phase>
                <goals>
                  <goal>eval</goal>
                </goals>
              </execution>
            </executions>
          </plugin>
          <plugin>
            <groupId>org.apache.maven.its.plugins</groupId>

        </configuration>
        <executions>
          <execution>
            <id>test</id>
            <phase>validate</phase>
            <goals>
              <goal>eval</goal>
            </goals>
            <configuration>
              <outputFile>pom.properties</outputFile>
            </configuration>
          </execution>
        </executions>
        <dependencies>

  <version>0.1</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-4193</name>
  <description>
    Test that multiple artifact repository declarations with the same id cause a validation error even if the
    repositories are defined within a (non-active) profile.
  </description>

  <profiles>
    <profile>
      <id>test</id>
      <repositories>
        <repository>
          <id>one</id>

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

  <name>Maven Integration Test :: MNG-3916</name>
  <description>
    Test that plugin executions are properly merged during inheritance, even if the child plugin section has no
    version.
  </description>

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

    <version>0.1</version>
  </parent>

  <artifactId>child</artifactId>

  <name>Maven Integration Test :: MNG-3943</name>
  <description>
    Test that plugin executions are properly merged during inheritance, even if the child uses a different
    plugin version than the parent.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>

        <artifactId>maven-it-plugin-expression</artifactId>
        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <phase>validate</phase>
            <goals>
              <goal>eval</goal>
            </goals>
            <configuration>
              <outputFile>target/pom.properties</outputFile>
              <expressions>
                <expression>project/properties</expression>

        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <phase>validate</phase>
            <goals>
              <goal>eval</goal>
            </goals>
            <configuration>
              <outputFile>target/pom.properties</outputFile>
              <expressions>
                <expression>project</expression>

        <artifactId>maven-it-plugin-expression</artifactId>
        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <phase>validate</phase>
            <goals>
              <goal>eval</goal>
            </goals>
            <configuration>
              <outputFile>target/extension.properties</outputFile>
              <expressions>
                <expression>project/build/extensions</expression>