Download Google Ads API Client JAR files with dependency

Search JAR files by class name

google-cloud-translate from group com.google.cloud (version 1.26.0)

Java idiomatic client for Google Cloud Translate

Group: com.google.cloud Artifact: google-cloud-translate

9 downloads

Artifact google-cloud-translate
Group com.google.cloud
Version 1.26.0

google-api-services-vision from group com.google.apis (version v1-rev346-1.22.0)

Group: com.google.apis Artifact: google-api-services-vision

9 downloads

Artifact google-api-services-vision
Group com.google.apis
Version v1-rev346-1.22.0

google-api-services-bigquery from group com.google.apis (version v2-rev391-1.21.0)

Group: com.google.apis Artifact: google-api-services-bigquery

9 downloads

Artifact google-api-services-bigquery
Group com.google.apis
Version v2-rev391-1.21.0

servlet-api from group org.apache.tomcat (version 6.0.51)

javax.servlet package

Group: org.apache.tomcat Artifact: servlet-api

9 downloads

Artifact servlet-api
Group org.apache.tomcat
Version 6.0.51

payara-api from group fish.payara.api (version 5.182)

Artefact that exposes public API of Payara Application Server

Group: fish.payara.api Artifact: payara-api

9 downloads

Artifact payara-api
Group fish.payara.api
Version 5.182

listenablefuture from group com.google.guava (version 1.0)

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