Update Guava and checker-qual.
Also, try yet again to get copy-dependencies working with Truth.
<!-- Properties for multiple-artifact deps. -->
<auto-value.version>1.6.3</auto-value.version>
- <checker-framework.version>2.5.5</checker-framework.version>
- <guava.version>27.0.1</guava.version>
+ <guava.version>28.1</guava.version>
<gwt.version>2.8.2</gwt.version>
<protobuf.version>3.10.0</protobuf.version>
<!-- Property for protobuf-lite protocArtifact, which isn't a "normal" Maven dep. -->
<dependency>
<groupId>org.checkerframework</groupId>
<artifactId>checker-compat-qual</artifactId>
- <version>${checker-framework.version}</version>
+ <version>2.5.5</version>
</dependency>
<dependency>
<groupId>org.checkerframework</groupId>
<artifactId>checker-qual</artifactId>
- <version>${checker-framework.version}</version>
+ <version>2.8.1</version>
</dependency>
<dependency>
<groupId>junit</groupId>
<groupId>com.google.truth.extensions</groupId>
<artifactId>truth-java8-extension</artifactId>
</exclusion>
+ <!--
+ Possibly dangerous hack: Exclude a system dependency that Maven
+ tries to download when we run copy-dependencies, despite our
+ various attempts to make it not do that.
+
+ I'm surprised that Truth's Compile-Testing-based tests still work
+ with this exclusion in place. But they seem to, so... yay?
+
+ TODO(b/28340920): Remove this exclusion after we move off the
+ internal Maven mirror for which we run copy-dependencies.
+
+ (Or we could consider copying Compile-Testing's system dependency
+ into Truth in test scope, and *maybe* we can get copy-dependencies
+ to exclude it once it's part of the Truth pom??)
+ -->
+ <exclusion>
+ <groupId>com.sun</groupId>
+ <artifactId>tools</artifactId>
+ </exclusion>
</exclusions>
</dependency>
<dependency>
