- Notifications
You must be signed in to change notification settings - Fork11.1k
Google core libraries for Java
License
google/guava
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
Guava is a set of core Java libraries from Google that includes new collectiontypes (such as multimap and multiset), immutable collections, a graph library,and utilities for concurrency, I/O, hashing, primitives, strings, and more! Itis widely used on most Java projects within Google, and widely used by manyother companies as well.
Guava comes in two flavors:
- The JRE flavor requires JDK 1.8 or higher.
- If you need support for Android, usethe Android flavor. You canfind the Android Guava source in the
androiddirectory.
Guava's Maven group ID iscom.google.guava, and its artifact ID isguava.Guava provides two different "flavors": one for use on a (Java 8+) JRE and onefor use on Android or by any library that wants to be compatible with Android.These flavors are specified in the Maven version field as either33.5.0-jre or33.5.0-android. For more about depending on Guava, seeusing 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>33.5.0-jre</version><!-- or, for Android:--> <version>33.5.0-android</version></dependency>
To add a dependency using Gradle:
dependencies {// Pick one:// 1. Use Guava in your implementation only: implementation("com.google.guava:guava:33.5.0-jre")// 2. Use Guava types in your public API: api("com.google.guava:guava:33.5.0-jre")// 3. Android - Use Guava in your implementation only: implementation("com.google.guava:guava:33.5.0-android")// 4. Android - Use Guava types in your public API: api("com.google.guava:guava:33.5.0-android")}
For more information on when to useapi and when to useimplementation,consult theGradle documentation on API and implementation separation.
Snapshots of Guava built from themaster branch are available through Mavenusing version999.0.0-HEAD-jre-SNAPSHOT, or999.0.0-HEAD-android-SNAPSHOTfor the Android flavor.
Snapshot API Javadoc as well asSnapshot API Diffs are also available.
Another easy way to get to the Javadoc is to openguava.dev/api. You can also jump right to a specificclass by appending the class name to guava.dev. For example,guava.dev/ImmutableList!
- Our users' guide,Guava Explained
- A nice collection ofother helpful links
- GitHub project
- Issue tracker: Report a defect or feature request
- StackOverflow: Ask "how-to" and "why-didn't-it-work" questions
- guava-announce: Announcements of releases and upcoming significant changes
- guava-discuss: For open-ended questions and discussion
APIs marked with the
@Betaannotation at the class or method level aresubject to change. They can be modified in any way, or even removed, at anytime. If your code is a library itself (i.e., it is used on the CLASSPATH ofusers outside your own control), you should not use beta APIs unless yourepackage them.If your code is a library, we strongly recommend usingtheGuava Beta Checker to ensure that you do not use any@BetaAPIs!APIs without
@Betawill remain binary-compatible for the indefinitefuture. (Previously, we sometimes removed such APIs after a deprecationperiod. The last release to remove non-@BetaAPIs was Guava 21.0.) Even@DeprecatedAPIs will remain (again, unless they are@Beta). We have noplans to start removing things again, but officially, we're leaving ouroptions open in case of surprises (like, say, a serious security problem).Guava has one dependency that is needed for linkage at runtime:
com.google.guava:failureaccess:1.0.3. It also hassome annotation-only dependencies, which we discuss in moredetail at that link.Serialized forms of ALL objects are subject to change unless notedotherwise. Do not persist these and assume they can be read by a futureversion of the library.
Our classes are not designed to protect against a malicious caller. Youshould not use them for communication between trusted and untrusted code.
For the mainline flavor, we test the libraries using OpenJDK 8, 11, and 17on Linux, with some additional testing on newer JDKs and on Windows. Somefeatures, especially in
com.google.common.io, may not work correctly innon-Linux environments. For the Android flavor, our unit tests also run onAPI level 23 (Marshmallow).
About
Google core libraries for Java
Topics
Resources
License
Code of conduct
Contributing
Security policy
Uh oh!
There was an error while loading.Please reload this page.