[
https://issues.apache.org/jira/browse/NIFI-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908574#comment-14908574
]
Matt Gilman commented on NIFI-999:
----------------------------------
Semi related to this effort is the request to support multiple versions of the
same extension (possibly through the use of a label/tag) [1].
[1]
https://cwiki.apache.org/confluence/display/NIFI/Multiple+Versions+of+the+Same+Extension
> "Tag" extensions based on their designated NiFi API version
> -----------------------------------------------------------
>
> Key: NIFI-999
> URL: https://issues.apache.org/jira/browse/NIFI-999
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Aldrin Piri
>
> Extensions need some form of tagging, whether it is on an individual
> processor basis via annotation or at the NAR level to specify the version of
> NiFi they were built against.
> The idea is to catch those processors at server start (or potentially,
> additionally) at the point of assembly with a Maven plugin) that may be using
> incompatible APIs.
> While the importance of this will not be realized until 1.0 and the
> introduction of breaking changes, a mechanism to ensure this is present for
> an extension to be valid should be initialized now so that standards are in
> place.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
