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

  <repositories>
    <repository>
      <id>one</id>
      <url>https://repo1.maven.org/maven2</url>
    </repository>
    <repository>
      <id>one</id>

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

  <artifactId>child</artifactId>

  <name>Maven Integration Test :: MNG-3938</name>
  <description>
    Test that plugin executions with the same id are merged during inheritance, especially executions using the
    default id, regardless whether the id is given explicitly by the user or implicitly assumed from defaults.
  </description>

  <build>
    <plugins>

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

    precisely control parts of the extension and dependencies to expose in the API class loader.
    Maven uses Plexus Classworlds to build the class loader hierarchy, therefore some concepts used in this extensions
    stem from Plexus Classworlds originally.
    <p><i>Notice:</i> this documentation is generated from a Modello model but the code executed is not generated

  <name>Maven Integration Test :: MNG-3900</name>
  <description>
    Test that build properties defined via active profiles are used for
    interpolation.
  </description>

  <!--
    These are some POM elements we would like to interpolate with
    properties from the profile.
  -->
  <url>https://maven.apache.org/${test}
  </url>
  <properties>
    <test>FAILED</test>
    <property>${test}</property>

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

  <dependencies>
    <dependency>
      <groupId>com.sun</groupId>
      <artifactId>tools</artifactId>
      <version>1.4.2</version>
      <scope>system</scope>
      <systemPath>${jre.home}/../lib/tools.jar</systemPath>
    </dependency>
  </dependencies>

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

  <dependencies>
    <dependency>
      <groupId>com.sun</groupId>
      <artifactId>tools</artifactId>
      <version>1.4.2</version>
      <scope>system</scope>
      <systemPath>${jre.home}/../lib/tools.jar</systemPath>
    </dependency>
  </dependencies>

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

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

  <artifactId>child</artifactId>

  <name>Maven Integration Test :: MNG-3938</name>
  <description>
    Test that plugin executions with the same id are merged during inheritance, especially executions using the
    default id, regardless whether the id is given explicitly by the user or implicitly assumed from defaults.
  </description>

  <build>
    <plugins>

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

  <name>Maven Integration Test :: MNG-3925</name>
  <description>
    Test that plugin executions (in the same phase) are properly ordered after inheritance/merge with
    parent executions.
  </description>

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