Eap maven plugin version is so far not kept in manifest. This issue is request to add eap maven plugin version to manifest.

That can provide explicit single source of truth:

• BOM generated from manifest can contain plugin version. That BOM can be used by customers for managing proper version of plugin. Nowadays on OpenShift, in future may expand to bare metal use case as well.
  • This was invalid argument. BOM can't be used for plugin version management.
• Internally can serve as unique contract between productization and QE which plugin should be tested. No confusion anymore about UMB content or repo content.
  • (happened recently there were multiple version of plugin in repo, it was not sure which to use)
  • When productizing image PROVISIONING_MAVEN_PLUGIN_VERSION can be set from manifest
• Plugin working with manifest containing newer version of plugin can emit warning, that it should be updated.

Today we communicate to cusomer use plugin version, which is present in delivered repo. That is not ideal.

I looked around and did not found we talked about it before. What do you think? Is there any particular hurdle we do not want to incorporate plugin version into manifest?

• E.g. from design perspective it is not part of server so we do not want it in manifest?