[
https://issues.apache.org/jira/browse/NIFI-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933370#comment-14933370
]
Bryan Bende commented on NIFI-976:
----------------------------------
Was looking at this briefly, and based on the way archetype properties work, I
think the main option here is to remove the default values for the nifiVersion
property in both archetypes. This way there is nothing that needs to stay in
sync on releases, and the user just has to provide the appropriate nifi version.
I investigated other options such as referencing ${archetypeVersion} or
$[project.version} in the template pom file for the bundle, but in both cases
it was unable to resolve those properties. In order to use ${project.version}
we would have to use resource filtering at build time of the archetype, but
this gets messy because then it also tries to filter in values for groupId and
artifactId which we don't want filtered at build time.
[~markap14] thoughts on removing the default version?
> Archetypes have a default nifiVersion that does not get updated on releases
> ---------------------------------------------------------------------------
>
> Key: NIFI-976
> URL: https://issues.apache.org/jira/browse/NIFI-976
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
>
> It would be nice if the nifiVersion property in the archetype-metadata.xml of
> the archetypes could come from ${project.version} or some property that gets
> updated on releases. Otherwise they are stuck on old snapshot versions, which
> doesn't prevent anything from working, but is not as user friendly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
