[
https://issues.apache.org/jira/browse/APEXCORE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972063#comment-15972063
]
Pramod Immaneni commented on APEXCORE-699:
------------------------------------------
Thanks for checking this. What if the version that the plugin returns is an
enum that is defined by the framework, then the user can't return some random
version number that the framework will not know what to do with. Second you
could have a convenience constant like CURRENT_VERSION (equivalent to the
VERSION variable above) that the user can simply use in their plugin for
convenience. Regd, the base class, if we put getVersion in the BasePlugin
(provided by the engine) and they extend it, aren't we back to the same problem
when the new version of the engine has a newer base class.
> Investigate versioning for plugins
> ----------------------------------
>
> Key: APEXCORE-699
> URL: https://issues.apache.org/jira/browse/APEXCORE-699
> Project: Apache Apex Core
> Issue Type: Sub-task
> Reporter: Pramod Immaneni
> Assignee: Tushar Gosavi
> Priority: Minor
>
> Having versioning information in the plugin would help in dealing with
> compatibility with older plugins when the plugin interface changes. This
> needs to be investigated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
