- (#32 - When tagging an image, the plugin might skip one or more steps due to unexpected multiline output for a build step)
- (#35) Introduced option to configure a batch of images to build, tag and push
- (#38 The plugin now checks
~/.docker/config.json
for credentials. - (#36) Implemented a retry mechanism for Podman push
- This plugin now requires Java 8 rather than Java 9.
- Documentation has now moved towards Github Pages.
- (#28) Changed algorithm for image hash detection when using multistage containerfiles to use lookahead instead of look back.
- (#30) Introduced
pullAlways
option in build configuration whether an image should always be pulled. More information.
- (#26) Introduced
pull
option in build configuration to control whether an image should be pulled. More information. Thanks to Christopher J. Uwe.
- When debug is enabled, Podman version information will now be printed.
- Passwords that contained special characters were not always properly obfuscated
- Set the default run directory to the root of the current module instead of the root of the Maven project.
- Allow configuration of the directory where the Podman command is executed. This defaulted to the target directory, which is not always convenient.
- Introduced a flag called
failOnMissingContainerFile
that prevents that the plugin fail throw an exception in case no Containerfile is present in a Maven module. This may be useful for projects that use this plugin as part of a profile where aContainerfile
is not always in the same location
- Fixed an issue that required the
CleanMojo
to have a valid ImageConfiguration. This is not necessary since only the custom root storage location needs to be configured for this Mojo to work.
- Renamed
Docker
toContainer
to be in line with Podman's naming conventions. This is a breaking change, please update your configuration. - Added basic support for multistage
Containerfile
s. Please refer to documentation for the exact configuration.
- Added configuration of the
--runroot
setting, which is used by Podman to store its state information.
- Added clean phase that allows cleaning up the local storage. This only works when the root storage location is configured in the pom file to prevent accidentally deleting unrelated files.
- Fixed a NullPointerException that occurred when no image configuration was present in the pom. A normal exception with more information is now raised instead.
- Added possibility to build container images with docker manifest and configuration data (
podman build --format=<oci/docker>
equivalent).
- Fixed a
NullPointerException
that could occur when no<podman/>
configuration was specified.
- Added option to set a custom root directory when running Podman (equivalent of running
podman --root=/some/custom/directory
)
- Labels were not always added on a new line
- Labels after an
ENTRYPOINT
command were sometimes ignored. Labels are now put on the line after the base image declaration (FROM
command)
- Documentation no longer states that this plugin is not in Maven Central.
- Podman used the wrong base dir for building container images
- When TLS Verify is not set, this sometimes caused an '... takes only 1 argument' error, due to an empty subcommand being passed.
- Changed the log line that says 'Initializing image configurations.' to debug.
- Explicitly set
dockerFileDir
to value of${project.baseDir}
rather thennew File(".")
- AuthenticationService now checks the default credential file based on the XDG_RUNTIME_DIR environment variable
- When TLS Verify is not set, it will no longer be used when running Podman commands.
- When Podman login failed, the password of the user was printed in the error message
- Moved authentication to the different Mojo's, such that
skipBuild
,skipPush
,skipSave
can be configured separately.
- Removed accidental publication of passphrase. Tag 0.2.0 has therefore been removed from Github.
- Refactored the iamge build configuration for more flexibility
- Added noCache support when buildig images
- Added support for labels. Labels are metadata and will be appended to the source Dockerfile before running a build
NOTE: This release is not compatible with 0.1.0. Due to the early stages of development you must reconfigure your plugin in the pom.xml
Initial implementation released