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-....
Add to your project9999.0-empty-to-avoid-conflict-with-guava
<dependency>
<groupId>com.google.guava</groupId>
<artifactId>listenablefuture</artifactId>
<version>9999.0-empty-to-avoid-conflict-with-guava</version>
</dependency>Version Details — 9999.0-empty-to-avoid-conflict-with-guava
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-....
Loading historical trends...
Badges
Version Badge
[](https://modernmvn.com/artifact/com.google.guava/listenablefuture)
<a href="https://modernmvn.com/artifact/com.google.guava/listenablefuture"><img src="/badge/com.google.guava/listenablefuture" alt="Maven Version" /></a>
.. image:: /badge/com.google.guava/listenablefuture :target: https://modernmvn.com/artifact/com.google.guava/listenablefuture :alt: Maven Version
Security Badge
[](https://modernmvn.com/artifact/com.google.guava/listenablefuture)
<a href="https://modernmvn.com/artifact/com.google.guava/listenablefuture"><img src="/api/security/com.google.guava/listenablefuture/9999.0-empty-to-avoid-conflict-with-guava/badge.svg" alt="Security" /></a>
.. image:: /api/security/com.google.guava/listenablefuture/9999.0-empty-to-avoid-conflict-with-guava/badge.svg :target: https://modernmvn.com/artifact/com.google.guava/listenablefuture :alt: Security