Details
-
Task
-
Resolution: Done
-
L3 - Default
-
None
-
None
Description
Context:
With OPT-2188 we introduced a breaking change to the import plugin api. (new tenantId field, if a plugin creates new instances of a variable it might miss a set tenant in from the original variable instance if the plugin is based on an older plugin library)
In order to fail starting optimize if a configured plugin is based on an incompatible version of the plugin api we need a plugin version check in place that performs this check.
AT:
- Optimize 2.6.0 does not start if a plugin is based on a optimize plugin dependency <2.6.0
- There is a meaningful error message to tell the user what the problem is and how to fix it
- The Optimize example project plugins are updated and it is described that it is necessary to include the Optimize version in the jar manifest
- The technical documentation is updated to include the information that it is necessary to build plugins with the correct Optimize version and to include the Optimize version in the jar manifest