This weekend, openjdk bumped their debian base images from stretch to buster, bringing in a few package and language tool changes.
Currently all PRs are red on travis. For local dev using the docker tools, it will probably break if you pull the new new openjdk:11 image (or openjdk:8 for branch-1.9) Ismael raised https://issues.apache.org/jira/browse/AVRO-2732 for Java 8 (thanks!), but it looks like there are also issues with Ruby and python. I'd like to see a quick fix to unblock this, and I'm looking into two strategies: (1) moving our tools/build forward for the newer, more stabler, more secure tools in the new openjdk image and (2) unbumping the base image back to more familiar debian-stretch. Some other points: * For Java artifacts built on Apache jenkins, the `mvn install` on https://builds.apache.org/blue/organizations/jenkins/AvroJava/ should still be OK of course. * If you build locally and you don't pull the new openjdk base images, you should be OK. * If you build locally and don't use the docker tools, that should be fine too. For the ongoing 1.9.2 RC2, there shouldn't be any changes to the released artifacts and code, but the docker image on the release-1.9.2-rc2 tag no longer works (note that this is also true for the docker image on release-1.9.1 tag). We can probably have a longer conversation about The Right Thing To Do for the future with respect to reproducibility, travis, yetus, docker, tools, etc! All my best, Ryan
