[
https://issues.apache.org/jira/browse/NIFI-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373406#comment-15373406
]
Joseph Witt commented on NIFI-2225:
-----------------------------------
For the first mention of version references keep in mind the release plugin and
process automatically takes care of the version references so for the
programmer they only have to enter them the first time. I agree though it
would be ideal to have only one. I think due to perhaps maven issues in older
versions of maven or improper use of maven we found the behavior to be
problematic while doing releases so we went with explicit references. Probably
could fix that now.
For the second point I'd suggest that there is no need for a specific nifi
version reference there. Backward compatibility for extensions is a pretty
firmly held item and has defined major release behaviors. The compatibility is
to the series/version of the nifi-api as well and not nifi itself. As we
tackle the extension repository I think we can also more meaningfully capture
this information too if needed.
> Improvement to archetypes and version management
> ------------------------------------------------
>
> Key: NIFI-2225
> URL: https://issues.apache.org/jira/browse/NIFI-2225
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 0.6.1
> Reporter: Stephane Maarek
> Priority: Minor
>
> Hi,
> Just done writing my first processor and there are two things I think could
> be improved:
> - The version number is defined in three pom.xml. I believe it should only be
> defined in the parent one and the children should inherit it (under the tag
> <parent>). This will decrease the number of changes that need to happen when
> a new version appears
> - There should be a separate parameter for NiFi version vs processor version
> I.e. the final nar would be:
> processor-name.<processor version>.<nifi version>.nar
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
