In order to simplify future migration and for user to always be using the correct EAP Maven Plugin, we should document the usage of the PROVISIONING_MAVEN_PLUGIN_VERSION in the user pom.xml has we are doing e.g. here. That mean option instead of specifying plugin version explicitly

        <plugins>
            <plugin>
                <groupId>org.jboss.eap.plugins</groupId>
                <artifactId>eap-maven-plugin</artifactId>
                <version>2.0.0.Beta1-redhat-00001</version>
                <configuration>
                    <feature-packs>
                        <feature-pack>

leverage environment variable resolution of ${env.PROVISIONING_MAVEN_PLUGIN_VERSION}.

        <plugins>
            <plugin>
                <groupId>org.jboss.eap.plugins</groupId>
                <artifactId>eap-maven-plugin</artifactId>
                <version>${env.PROVISIONING_MAVEN_PLUGIN_VERSION}</version>
                <configuration>
                    <feature-packs>
                        <feature-pack>

env.PROVISIONING_MAVEN_PLUGIN_VERSION is up to date with each image release as latest available plugin version. And that combination is also tested. If customer feels unconfortable to consume plugin version changes with new images, it can be always fixed to some particular version and have that fully under control.