Plugin MigrateMojo to automate migration from FMP to JKube

[manusa]

Description

In order to increase the adoption of the plugin we can create a MigrateMojo that will automatically update any pom.xml so that it uses Eclipse JKube instead of Fabric8 Maven Plugin.

Basically, any time the command mvn org.eclipse.jkube:kubernetes-maven-plugin:migrate is run in a Maven project root directory, the pom.xml file is parsed and appropriate substitutions are made.

Ideally, MigrateMojo should be "smart" enough to see if fabric8-maven-plugin should be replaced by kubernetes-maven-plugin or openshift-maven-plugin.

If the previous requirement is not possible or very difficult to implement, we can have an OpenshiftMigrateMojo that extends the basic MigrateMojo and overrides getArtifactId method to return openshift-maven-plugin instead of the super implementation kubernetes-maven-plugin.

The plugin should try to consider all configurations, flags and properties and rename them to match the new ones.

See also

• There was a MigrateMojo in FMP v3, maybe there's something useful there (or maybe not)