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

            </configuration>
          </plugin>
        </plugins>
      </build>
    </profile>
    <profile>
      <id>javac-for-jvm18plus</id>
      <activation>
        <!--
            In order to build and run the tests against JDK 18+, we need to pass java.security.manager=allow, to make
            the deprecated 'java.lang.SecurityManager' available for use.
         -->
        <jdk>[18,]</jdk>

            </configuration>
          </plugin>
        </plugins>
      </build>
    </profile>
    <profile>
      <id>javac-for-jvm18plus</id>
      <activation>
        <!--
            In order to build and run the tests against JDK 18+, we need to pass java.security.manager=allow, to make
            the deprecated 'java.lang.SecurityManager' available for use.
         -->
        <jdk>[18,]</jdk>