Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / guava / 52f6c94955d269d860f5f416ab783814823052e9
commit52f6c94955d269d860f5f416ab783814823052e9[log] [tgz]
authorcpovirk <cpovirk@google.com>Wed Aug 04 17:37:46 2021 -0700
committerGoogle Java Core Libraries <java-core-libraries-team+copybara@google.com>Wed Aug 04 17:40:25 2021 -0700
tree468374821f1e0720008c651f7b9d3dc6a61d198c
parent1d615ea9853a293abfac770e31db6955c483ea92 [diff]
Annotate most remaining classes in `collect` for nullness.

These classes aren't publicly visible, so this CL might not really matter to users (unless, of course, it help us find bugs before they affect users!). But to be sure, I'd want to verify that none have publicly visible subclasses. (I suspect that none do, but I haven't looked carefully.)

I skipped `MapMakerInternalMap`, which, like its successor `LocalCache`, I deemed to be too much trouble to be worth it. (Still, since I still added `MapMakerInternalMap` to the list of files to run through the nullness checker, I had to add `@SuppressWarnings("nullness")` on at least part of it, since it assigns `null` to a field that it also dereferences. Maybe it would have been nicer for me to suppress only where needed (or to use `requireNonNull`/`uncheckedCastNullableTToT`), leaving a comment about the safety of that particular operation. But I figured it was best to not give any impression that we're getting our usual automated nullness checking in the class. This is similar to what I did for `LocalCache` in CL 384759595.)

RELNOTES=n/a
PiperOrigin-RevId: 388823277
26 files changed
tree: 468374821f1e0720008c651f7b9d3dc6a61d198c
  1. .github/
  2. android/
  3. futures/
  4. guava/
  5. guava-bom/
  6. guava-gwt/
  7. guava-testlib/
  8. guava-tests/
  9. refactorings/
  10. util/
  11. .gitattributes
  12. .gitignore
  13. CONTRIBUTING.md
  14. CONTRIBUTORS
  15. COPYING
  16. cycle_suppress_list.txt
  17. javadoc-stylesheet.css
  18. pom.xml
  19. README.md
README.md

Guava: Google Core Libraries for Java

Latest release Build Status

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, caching, primitives, strings, and more! It is widely used on most Java projects within Google, and widely used by many other companies as well.

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 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 30.1.1-jre or 30.1.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>30.1.1-jre</version>
  <!-- or, for Android: -->
  <version>30.1.1-android</version>
</dependency>

To add a dependency using Gradle:

dependencies {
  // Pick one:

  // 1. Use Guava in your implementation only:
  implementation("com.google.guava:guava:30.1.1-jre")

  // 2. Use Guava types in your public API:
  api("com.google.guava:guava:30.1.1-jre")

  // 3. Android - Use Guava in your implementation only:
  implementation("com.google.guava:guava:30.1.1-android")

  // 4. Android - Use Guava types in your public API:
  api("com.google.guava:guava:30.1.1-android")
}

For more information on when to use api and when to use implementation, consult the Gradle documentation on API and implementation separation.

Snapshots and Documentation

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.

Learn about Guava

Links

IMPORTANT WARNINGS

  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 for linkage at runtime: com.google.guava:failureaccess:1.0.1. It also has some annotation-only dependencies, which we discuss in more detail at that link.

  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 test the libraries using only OpenJDK 8 and OpenJDK 11 on Linux. Some features, especially in com.google.common.io, may not work correctly in other environments. For the Android flavor, our unit tests also run on API level 15 (Ice Cream Sandwich).