<module>sub</module>
  </modules>

  <build>
    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.its.plugins</groupId>
          <artifactId>maven-it-plugin-class-loader</artifactId>
          <version>2.1-SNAPSHOT</version>
        </plugin>
      </plugins>
    </pluginManagement>
  </build>

  <profiles>
    <profile>
      <id>maven-core-it</id>
      <activation>

  </description>

  <build>
    <!-- NOTE: This parent does not use plugin management -->
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-class-loader</artifactId>
        <version>2.1-SNAPSHOT</version>
        <dependencies>
          <dependency>
            <groupId>org.apache.maven.its.mng3906</groupId>
            <artifactId>e</artifactId>

  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-class-loader</artifactId>
        <version>2.1-SNAPSHOT</version>
        <dependencies>
          <dependency>
            <groupId>org.apache.maven.its.mng3906</groupId>
            <artifactId>c</artifactId>

  </properties>

  <dependencyManagement>
    <!-- Not included:
         - apache-maven, as it delivers the binaries
         - maven-compat, only used by apache-maven distributions to support older releases
         - maven-slf4j-provider, only used by apache-maven distributions
         - maven-wrapper, only used by apache-maven-wrapper distributions -->
    <dependencies>
      <dependency>

    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
    use 9999.0-....

    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
    use 9999.0-....