The fabric8-maven-plugin has been deprecated (see https://github.com/fabric8io/fabric8-maven-plugin/blob/master/README.md) and Openshift support has been moved to the jkube openshift-maven-plugin (https://www.eclipse.org/jkube/docs/openshift-maven-plugin/). It would be good to move the quickstarts to use the jkube openshift-maven-plugin.
The way we use these maven plugins in Fuse is that we repackage them and give them the same version as the redhat-fuse BOM. This allows us to temporarily support both openshift-maven-plugin and fabric8-maven-plugin. We can move the quickstarts to use the jkube openshift-maven-plugin so that new applications built off of them and the archetypes will use that and as long as we also still include the fabric8-maven-plugin, developers will be able to update their older apps that use fabric8-maven-plugin to the newest version of Fuse simply by updating the fuse-bom-version as they do now.
The strategy I've taken here is to include a property in the openshift profile that specifies the Fuse image :
We can either do this or, or fork openshift-maven-plugin and include the image names like we do here :
Proposing to fix this for 7.9.