Tad Cordle

That is true, but when you don't target a registry, Jib still caches base images locally to skip unnecessary pulls. So I think this issue is really only a problem...

On linux, the base image cache is at `$HOME/.cache/google-cloud-tools-java/jib`, unless you set `-Djib.useOnlyProjectCache=true`, in which case it uses the same cache in `build/` for both base image and application layers....

`jib.useOnlyProjectCache` is a system property without a corresponding configuration parameter, so I think you either need to pass it via commandline, or put it in a [`gradle.properties` file](https://docs.gradle.org/current/userguide/build_environment.html#sec:gradle_system_properties). It looks...

Would be nice to streamline the plugin integration test code a bit more as well in general. The tests themselves work fine, but they operate using a lot of awkward...

This ended up being a problem with the `com.github.johnrengelman.shadow` plugin using an older version of `asm`. Since this doesn't seem to be jib's fault, I'm going to close this. However,...

We may want to file an issue or PR at https://github.com/johnrengelman/shadow to upgrade their ASM dependency.

I think it's because of the progress bar

I don't think there's any harm in having an explicit entry for `/`, is there? Maybe we can just go with the quick fix you suggested.

FYI the podman issue is here: https://github.com/containers/libpod/issues/4646

Clearing the milestone on this, since it's low priority and turns out to not be as easy as we thought (using `isChanging()` means we need to find the `ExternalModuleDependency` object...