guava
GitHub describes it as Google core libraries for Java. The repository metadata lists Java as its primary language. The metadata lists the Apache-2.0 license. This article stays within the project description and details documented in the GitHub repository README.
google/guava: Guava: Google Core Libraries for Java
GitHub describes it as Google core libraries for Java. The repository metadata lists Java as its primary language. The metadata lists the Apache-2.0 license. This article stays within the project description and details documented in the GitHub repository README.
Repository scope
GitHub describes it as Google core libraries for Java. The repository metadata lists Java as its primary language. The metadata lists the Apache-2.0 license. The README describes the project this way: Guava is a set of core Java libraries from Google 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! It is widely used on most Java projects within Google, and widely used by many other companies as well.
Guava: Google Core Libraries for Java
The README section "Guava: Google Core Libraries for Java" states: The JRE flavor requires JDK 1.8 or higher. If you need support for Android, use the Android flavor. You can find the Android Guava source in the [ android directory].
Adding Guava to your build
The README section "Adding Guava to your build" states: 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 by any library that wants to be compatible with Android. These flavors are specified in the Maven version field as either 33.6.0-jre or 33.6.0-android . For more about depending on Guava, see [using Guava in your build].
Adding Guava to your build
The README section "Adding Guava to your build" states: For more information on when to use api and when to use implementation , consult the Gradle documentation on API and implementation separation.
Editorial conclusion
The repository README is the source for this review. It does not replace a local installation or an independent test.
Community notes