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

  <name>Maven Integration Test :: MNG-3906</name>
  <description>
    Test that project-level plugin dependencies are properly merged during inheritance.
  </description>

  <build>
    <!-- NOTE: This parent uses plugin management -->
    <pluginManagement>
      <plugins>
        <plugin>

  <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 does not use plugin management for the test plugin -->
    <plugins>
      <plugin>

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

  <artifactId>child</artifactId>

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

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

  <name>Maven Integration Test :: MNG-4129</name>
  <description>
    Verify that plugin executions defined in the parent with inherited=false are not executed in child modules.
  </description>

  <modules>
    <module>child-1</module>
    <module>child-2</module>
  </modules>

  <build>
    <plugins>
      <plugin>

    version number is enough for some build systems (notably, Gradle) to select
    that empty artifact over the "real" listenablefuture-1.0 -- avoiding a
    conflict with the copy of ListenableFuture in guava itself. If users are
    using an older version of Guava or a build system other than Gradle, they
    may see class conflicts. If so, they can solve them by manually excluding
    the listenablefuture artifact or manually forcing their build systems to

  <groupId>org.apache.maven.its.mng1995</groupId>
  <artifactId>test1</artifactId>
  <version>1.0</version>

  <name>Maven Integration Test :: MNG-1995</name>
  <description>
    Verify that POM fields that are of type boolean can be interpolated with expressions.
  </description>

  <properties>
    <filter.resources>true</filter.resources>
    <releasesEnabled>true</releasesEnabled>
  </properties>

  <repositories>

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

  <name>Maven Integration Test :: MNG-3899</name>
  <description>
    Test that build extensions are properly merged during inheritance.
  </description>

  <build>
    <extensions>
      <extension>
        <groupId>org.apache.maven.its.mng3899</groupId>
        <artifactId>a</artifactId>

  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-4193</name>
  <description>
    Test that multiple plugin 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>
      <pluginRepositories>
        <pluginRepository>
          <id>one</id>

  </parent>

  <artifactId>child-1</artifactId>

  <name>Maven Integration Test :: MNG-3937</name>
  <description>
    Test that during inheritance/merging of a plugin execution the goals specified by child and parent are properly
    ordered.
  </description>

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

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

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