commit | 13e39cd167a49aad525be462e61d9e5f2b1781ec | [log] [tgz] |
---|---|---|
author | jrtom <jrtom@google.com> | Mon Jul 30 19:07:24 2018 -0700 |
committer | Colin Decker <cgdecker@google.com> | Wed Aug 01 16:02:17 2018 -0400 |
tree | 94ce0babed608f23bc849c5cefeb0d1e632f1356 | |
parent | fdc342613ba3f2e94b23e4912671af4744fbf8cc [diff] |
Change to some TODOs caused by some internal change. RELNOTES=n/a ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=206688194
Guava is a set of core libraries that includes new collection types (such as multimap and multiset), immutable collections, a graph library, functional types, an in-memory cache, and APIs/utilities for concurrency, I/O, hashing, primitives, reflection, string processing, and much 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 25.1-jre
or 25.1-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>25.1-jre</version> <!-- or, for Android: --> <version>25.1-android</version> </dependency>
To add a dependency using Gradle:
dependencies { compile 'com.google.guava:guava:25.1-jre' // or, for Android: api 'com.google.guava:guava:25.1-android' }
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).
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).