<artifactId>b</artifactId>
  <version>1.0</version>

    <build>
        <filters>
            <filter>src/main/filters/a.properties</filter>
            <filter>src/main/filters/c.properties</filter>
            <filter>src/main/filters/b.properties</filter>
            <filter>src/main/filters/d.properties</filter>
        </filters>
    </build>

  <description>
    Verify that paths to project directories use the platform-specific file separator.
  </description>

  <build>
    <filters>
      <filter>src/main/filters/it.properties</filter>
    </filters>
  </build>

        </includes>
        <excludes>
          <exclude>test.excluded</exclude>
        </excludes>
      </testResource>
    </testResources>
    <filters>
      <filter>src/main/filter/it.properties</filter>
    </filters>

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

          <configuration>
            <includes>
              <include>${test.include}</include>
            </includes>
            <!-- By having our own entries here, we also override the default exclusion filter, which excludes all nested classes. -->
            <excludes>
              <!-- https://github.com/google/guava/issues/2840 -->
              <exclude>%regex[.*PackageSanityTests.*.class]</exclude>

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

  <description>
    Verify that filter definitions are properly merged.
  </description>

  <build>
    <filters>
      <!-- NOTE: The first filter is deliberately defined by the child as well, so should not be added twice -->
      <filter>src/main/filters/child-a.properties</filter>
      <filter>src/main/filters/parent-c.properties</filter>
      <filter>src/main/filters/parent-b.properties</filter>

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