docker-maven-plugin moves on

February 24, 2016

rhuss/docker-maven-plugin is dead, long live fabric8io/docker-maven-plugin !

If you follow the Docker Maven Plugin Scene1, you probably noticed that there has been quite some progress in the last year. Started as a personal research experiment early 2014, rhuss/docker-maven-plugin (d-m-p) has took off a little bit. With more than 300 GitHub stars it’s now the second most popular docker-maven-plugin. With 38 contributors we were able to do 36 releases. It is really fantastic to see that many people contributing to a rather niche product. Many kudos go out to Jae for his many contributions and continued support on fixing and answering issues. Thanks also for always being very patient with my sometimes quite opinionated and picky code reviews :)

However it is now time to ignite the next stage and bring this personal ‘pet’ project to a wider context. And what is better suited here than the fabric8 community ?

Fabric8 is a next generation DevOps and integration platform for Docker based applications, with a focus on Kubernetes and OpenShift as orchestration and build infrastructure. Its a collection of multiple interrelated projects including Maven tooling for interacting with Kubernetes and OpenShift. d-m-p is already included as foundation for creating Docker application images.

I’m very happy that d-m-p has now found its place in this ecosystem where it will continue to flourish even faster.

The fabric8 community is very open and has established multiple communications channels on which you will find d-m-p now, too:

  • #fabric8 on is an IRC channel with a lot of helpful hands (including myself)
  • A mailing list for more in depth discussions
  • Issues are still tracked with GitHub issues
  • d-m-p specific blog posts will go out on the fabric8 blog in the future.

So, what changed ?

  • rhuss/docker-maven-plugin has been transferred to fabric8io/docker-maven-plugin
  • The Maven group id has changed from org.jolokia to io.fabric8 for all releases 0.14.0 and later.
  • CI and release management will be done on the fabric8 platform.

And what will not change ?

  • d-m-p will always be usable with plain Docker, speaking either to a remote or local Docker daemon. No Kubernetes, no OpenShift required.
  • I’ll continue to work on d-m-p ;-)

Thanks so much for all the fruitful feedback and pull requests. Keep on rocking ;-)

  1. with more than 15 docker-maven-plugins its probably fair to call it a “scene” ;-)