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>
  <build>
    <plugins>
      <plugin>

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

          <show>package</show>
        </configuration>
      </plugin>

          </tags>

          <!-- TODO(cpovirk): Move this to the parent after making the package-list files available there. -->
          <!-- We add the link ourselves, both so that we can choose Java 9 over the version that -source suggests and so that we can solve the JSR305 problem described below. -->
          <detectJavaApiLink>false</detectJavaApiLink>
          <offlineLinks>

                   JDK8 APIs. However, I assume (but did not confirm) that we'd
                   have the same issue with our -android builds, which need
                   animal-sniffer so that they can check that we're sticking to
                   JDK6-like APIs.

                   So instead, we use javac9, which doesn't lead to this error.
              -->
              <compilerArgs combine.children="append">