Always have image tag with the project.version

Description

When we are working with Docker registry provided by Nexus for release, the registry disabled the “redeploy”, so every image with the same version/tag can only be pushed once.

But the docker-maven-plugin always generate the tag with the POM’s project version. E.g. the POM is version 1.0, and with a continuous build number as 8, I specify the tag with

<tags>
  <tag>${project.version}.${build.number}</tag>
</tags>

The plugin always generates two tags 1.0 and 1.0.8, and tries to push both to registry. Apparently the push of 1.0 must fail, since it’s already pushed to registry together with previous builds, like 1.0.1.

I think it needs a way to disable the default tag of project.version, so I can specify only the intended tags.

Info

• d-m-p version : 0.20.1
• Maven version (mvn -v) : 3.0.5
• Docker version : 1.12.6

[meggarr]

@rhuss maybe I find another issue, when I tried to build and push in single command,

 mvn clean package docker:build docker:push -Ddocker.push.registry=<my-registry> -Ddocker.skip.tag=true

it tries to push the tags even they are skipped in build. It looks push does not respect docker.skip.tag=true. Is it a bug?

[meggarr]

#869