com.google.guava:listenablefuture

An empty artifact that Guava depends on to signal that it is providing ListenableFuture -- but is also available in a second "version" that contains com.google.common.util.concurrent.ListenableFuture class, without any other Guava classes. The idea is: - If users want only ListenableFuture, they depend on listenablefuture-1.0. - If users want all of Guava, they depend on guava, which, as of Guava 27.0, depends on listenablefuture-9999.0-empty-to-avoid-conflict-with-guava. The 9999.0-... 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 use 9999.0-....

Recommended: 9999.0-empty-to-avoid-conflict-with-guava 2 versions jar Updated 7 years agoChecking...

Add to your project1.0

<dependency>
    <groupId>com.google.guava</groupId>
    <artifactId>listenablefuture</artifactId>
    <version>1.0</version>
</dependency>

Version Details — 1.0

Packaging
jar
Direct Deps
0
Total Deps
0
Published
Sep 11, 2018
License
Unknown

Contains Guava's com.google.common.util.concurrent.ListenableFuture class, without any of its other classes -- but is also available in a second "version" that omits the class to avoid conflicts with the copy in Guava itself. The idea is: - If users want only ListenableFuture, they depend on listenablefuture-1.0. - If users want all of Guava, they depend on guava, which, as of Guava 27.0, depends on listenablefuture-9999.0-empty-to-avoid-conflict-with-guava. The 9999.0-... 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 use 9999.0-....

Checking security advisories...

Loading historical trends...

Badges

Version Badge

Preview:Maven version badge for listenablefuture
markdown
[![Maven Version](/badge/com.google.guava/listenablefuture)](https://modernmvn.com/artifact/com.google.guava/listenablefuture)
html
<a href="https://modernmvn.com/artifact/com.google.guava/listenablefuture"><img src="/badge/com.google.guava/listenablefuture" alt="Maven Version" /></a>
rst
.. image:: /badge/com.google.guava/listenablefuture
   :target: https://modernmvn.com/artifact/com.google.guava/listenablefuture
   :alt: Maven Version

Security Badge

Preview:Security badge for listenablefuture
markdown
[![Security](/api/security/com.google.guava/listenablefuture/1.0/badge.svg)](https://modernmvn.com/artifact/com.google.guava/listenablefuture)
html
<a href="https://modernmvn.com/artifact/com.google.guava/listenablefuture"><img src="/api/security/com.google.guava/listenablefuture/1.0/badge.svg" alt="Security" /></a>
rst
.. image:: /api/security/com.google.guava/listenablefuture/1.0/badge.svg
   :target: https://modernmvn.com/artifact/com.google.guava/listenablefuture
   :alt: Security