commit | a1b3c06876803a0b0e5d2f16708e1328da1bac09 | [log] [tgz] |
---|---|---|
author | Chris Povirk <cpovirk@google.com> | Thu Dec 26 22:06:54 2019 -0500 |
committer | Chris Povirk <cpovirk@google.com> | Thu Dec 26 22:06:54 2019 -0500 |
tree | 6a8fa1a3d1b8789ae8ca6994d127c5190b805835 | |
parent | bfc1cceca6dc6ea298aff1fb68e7655da16c2ec7 [diff] |
Reenable Javadoc for the GWT artifact for now. Without it, we get an error during Sonatype deployment: Missing: no javadoc jar found in folder '/com/google/guava/guava-gwt/28.2-jre'
Guava is a set of core libraries that includes new collection types (such as multimap and multiset), immutable collections, a graph library, and utilities for concurrency, I/O, hashing, primitives, strings, and more!
Guava comes in two flavors.
android
directory.Guava's Maven group ID is com.google.guava
and its artifact ID is guava
. Guava provides two different “flavors”: one for use on a (Java 8+) JRE and one for use on Android or Java 7 or by any library that wants to be compatible with either of those. These flavors are specified in the Maven version field as either 28.2-jre
or 28.2-android
. For more about depending on Guava, see using Guava in your build.
To add a dependency on Guava using Maven, use the following:
<dependency> <groupId>com.google.guava</groupId> <artifactId>guava</artifactId> <version>28.2-jre</version> <!-- or, for Android: --> <version>28.2-android</version> </dependency>
To add a dependency using Gradle:
dependencies { // Pick one: // 1. Use Guava in your implementation only: implementation("com.google.guava:guava:28.2-jre") // 2. Use Guava types in your public API: api("com.google.guava:guava:28.2-jre") // 3. Android - Use Guava in your implementation only: implementation("com.google.guava:guava:28.2-android") // 4. Android - Use Guava types in your public API: api("com.google.guava:guava:28.2-android") }
For more information on when to use api
and when to use implementation
, consult the Gradle documentation on API and implementation separation.
Snapshots of Guava built from the master
branch are available through Maven using version HEAD-jre-SNAPSHOT
, or HEAD-android-SNAPSHOT
for the Android flavor.
APIs marked with the @Beta
annotation at the class or method level are subject to change. They can be modified in any way, or even removed, at any time. If your code is a library itself (i.e. it is used on the CLASSPATH of users outside your own control), you should not use beta APIs, unless you repackage them. If your code is a library, we strongly recommend using the Guava Beta Checker to ensure that you do not use any @Beta
APIs!
APIs without @Beta
will remain binary-compatible for the indefinite future. (Previously, we sometimes removed such APIs after a deprecation period. The last release to remove non-@Beta
APIs was Guava 21.0.) Even @Deprecated
APIs will remain (again, unless they are @Beta
). We have no plans to start removing things again, but officially, we're leaving our options open in case of surprises (like, say, a serious security problem).
Guava has one dependency that is needed at runtime: com.google.guava:failureaccess:1.0.1
Serialized forms of ALL objects are subject to change unless noted otherwise. Do not persist these and assume they can be read by a future version of the library.
Our classes are not designed to protect against a malicious caller. You should not use them for communication between trusted and untrusted code.
For the mainline flavor, we unit-test the libraries using only OpenJDK 1.8 on Linux. Some features, especially in com.google.common.io
, may not work correctly in other environments. For the Android flavor, our unit tests run on API level 15 (Ice Cream Sandwich).