update to Guava 20.0
Basics
Logistics
Basics
Logistics
Description
Environment
None
Activity
Show:
Ian Young October 11, 2017 at 10:39 AM
Confirmed all the nightly and multi jobs are running just fine.
Ian Young October 10, 2017 at 11:13 AM
Per the discussion on the last developer call, I have run tests with both Java 7 and Java 8 on the parent project, java-support, java-idp-tomcat-base, jetty9-dta-ssl, trustany-ssl, xmlsectool, spring-extensions, java-opensaml, java-identity-provider. No test failures (after I fudged the unlimited crypto policy thing yet another time on my machine).
So, committed this change on maint-7 as commit 519ce77bef2fb98810f4ecf04350f1001bb39da5.
No change required on the v8 branch as it is already on Guava 23.0.
Jenkins now running checkin jobs, I will confirm this is done tomorrow if the nightly and multi jobs run OK.
The V7 parent POM designates Guava 19.0, which was released in 2015. There was one later V7-compatible version after that: Guava 20.0, released in October 2016.
We should update our V7 parent POM to use 20.0 for no other reason than to force any deprecations to be visible in the V3.4 IdP release.
The primary artifact for Guava 21 and later require Java 8, so won't be applicable to the V7 parent. There does seem to be an extra "Android" artifact for those versions that still works with V7, but making that kind of sideways migration seems too risky to me.
Release documentation: https://github.com/google/guava/wiki/Release20
API diffs: http://google.github.io/guava/releases/20.0/api/diffs/
That report shows no removed APIs, but some deprecations as well as a number of additions. I haven't checked to see whether the deprecations affect us directly.