Unification of docker-maven-plugin and fabric8-maven-plugin

The fabric8-maven-plugin is quite similar to this plugin. This plugins manage all facets for integrating Docker in the Maven build cycle. fabric8-maven-plugin does the same for Kubernetes and OpenShift and relies on docker-maven-plugin for generating the images.

There is quite some overlap in configuration (guess it’s around 80%) and since I’m working with both, I believe its a good idea to combine both. Unfortunately it is not possible to share configuration between plugins. A unification will widen the scope of this combined plugin, yes, but it will make it also much more powerful. For example, if we add finally docker-compose support we could easily map docker compose to Kubernetes configuration. For people using Kubernetes with Maven this would be a big, big win.

But before I start, I’d like to collect some opinions on that. Do you see any drawbacks when combining these plugins ? Do you also think its a good idea ?

Fire at will 😃

[rhuss]

This issue is quite old and a lot of things have happened in the meantime. The current status is:

• I have no ideas about Jenkins X and as it uses an orthogonal approach there will be no overlap
• d-m-p already went into f-m-p and is used for all plain Docker builds (but not s2i builds)
• The generator framework is still f-m-p only but it is planned to adopt it for d-m-p, too.
• The general vision is outlined in https://github.com/fabric8io/fabric8-build for a possible future of d-m-p and f-m-p

[rhuss]

Yes, there is a difference:

• f-m-p only exposes the “build” goal from d-m-p, nothing about “run” or any other goals.
• f-m-p adds OpenShift s2i capabilitites to the build, which are not available in d-m-p