Skip to content
Google core libraries for Java
Branch: master
Clone or download
carterkozak and kluever Fix ByteStreams.skipUpTo to avoid making unnecessary allocations.
- Fixes #3662
- Closes #3663


Created by MOE:
Latest commit cff0c80 Oct 18, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
android Fix ByteStreams.skipUpTo to avoid making unnecessary allocations. Oct 20, 2019
futures Replace with Jun 3, 2019
guava-bom Fix Apache license name in guava pom Jun 3, 2019
guava-gwt Require tokens to be non-empty. Oct 10, 2019
guava-testlib Bump version, which went out of date since the previous CL was created. Oct 2, 2019
guava-tests Add Stream support to Stats and StatsAccumulator. Oct 16, 2019
guava Fix ByteStreams.skipUpTo to avoid making unnecessary allocations. Oct 20, 2019
refactorings Open source refactorings directory. This is knowingly very simple, wi… Mar 28, 2018
util Fix snapshots (and snapshot javadoc/jdiff) to be created again. Aug 28, 2019
.gitattributes Add a .gitattributes file to control line ending normalization, which… Nov 4, 2014
.gitignore Add .DS_Store to .gitignore. Mar 30, 2016
.travis.yml Fix the travis build Jun 30, 2019 usage of American English spelling for "license" Oct 5, 2016
CONTRIBUTORS fix indentation Apr 14, 2011
COPYING fix indentation Apr 14, 2011 update failureaccess version to match docs with code Oct 14, 2019
cycle_whitelist.txt Fix nonpublic identifiers and documentation that use "whitelist" or "… Jun 12, 2018
javadoc-stylesheet.css Fix a couple of issues with JDK7 javadoc style by using a slightly cu… Jul 17, 2013
pom.xml switch to an internal annotation for ignoring JRE Oct 11, 2019

Guava: Google Core Libraries for Java

Latest release Build Status

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.

  • The JRE flavor requires JDK 1.8 or higher.
  • If you need support for JDK 1.7 or Android, use the Android flavor. You can find the Android Guava source in the android directory.

Adding Guava to your build

Guava's Maven group ID is 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.1-jre or 28.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:

  <!-- or, for Android: -->

To add a dependency using Gradle:

dependencies {
  compile ''
  // or, for Android:
  api ''


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.

  • Snapshot API Docs: guava
  • Snapshot API Diffs: guava

Learn about Guava



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

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

  3. Guava has one dependency that is needed at runtime:

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

  5. Our classes are not designed to protect against a malicious caller. You should not use them for communication between trusted and untrusted code.

  6. For the mainline flavor, we unit-test the libraries using only OpenJDK 1.8 on Linux. Some features, especially in, may not work correctly in other environments. For the Android flavor, our unit tests run on API level 15 (Ice Cream Sandwich).

You can’t perform that action at this time.