jib-maven-plugin

Major Changes

• HTTP redirection URLs are no longer sanitized in order to work around an issue with certain registries that do not conform to HTTP standards. This resolves an issue with using Red Hat OpenShift and Quay registries.
• Now automatically refreshes Docker registry authentication tokens when expired, fixing the issue that long-running builds may fail with "401 unauthorized."
• Now <containerizingMode>packaged works as intended with Spring Boot projects that generate a fat JAR.
• Removed deprecated <extraDirectory> configuration in favor of <extraDirectories>.
• Removed deprecated <container><useCurrentTimestamp> configuration in favor of <container><creationTime> with USE_CURRENT_TIMESTAMP.
• The default base image cache location has been changed on MacOS and Windows.
  • MacOS ($XDG_CACHE_HOME defined): from $XDG_CACHE_HOME/google-cloud-tools-java/jib/ to $XDG_CACHE_HOME/Google/Jib/
  • MacOS ($XDG_CACHE_HOME not defined): from $HOME/Library/Application Support/google-cloud-tools-java/jib/ to $HOME/Library/Caches/Google/Jib/
  • Windows ($XDG_CACHE_HOME defined): from $XDG_CACHE_HOME\google-cloud-tools-java\jib\ to $XDG_CACHE_HOME\Google\Jib\Cache\
  • Windows ($XDG_CACHE_HOME not defined): from %LOCALAPPDATA%\google-cloud-tools-java\jib\ to %LOCALAPPDATA%\Google\Jib\Cache\
  • Initial builds will be slower until the cache is repopulated, unless you manually move the cache from the old location to the new location
• Added json output file for image metadata after a build is complete. Writes to target/jib-image.json by default, configurable with <outputPaths><imageJson>.
• Fixed <extraDirectories><permissions> being ignored if <paths> are not explicitly defined.
• jib:buildTar with <container><format>OCI now builds a correctly formatted OCI archive.
• Now <containerizingMode>packaged correctly identifies the packaged JAR generated at a non-default location when configured with the Maven Jar Plugin's <classifier> and <outputDirectory>.
• When giving registry credentials in settings.xml, specifying port in <server><id> is no longer required.
• Fixed an issue where configuring the <warName> property of the Maven WAR plugin fails the build.

See CHANGELOG.md for more details.