[
https://issues.apache.org/jira/browse/NIFI-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535573#comment-16535573
]
ASF GitHub Bot commented on NIFI-5383:
--------------------------------------
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2848
I see a couple errant uses in nifi-hbase pom(s) but otherwise it is all ok
usage.
In your evaluation of things looking ok it would have been a typical build
I suspect. But we need consistency for maintainability purposes of course and
further we have it this way because this way works not just during typical
build processes developers do but also it worked well in maven during the
apache release process. We can change it but doing so requires a far more
thorough analysis of not just the typical build process but being able to do a
full release cycle.
It is not necessary, however, to use '${project.version}' since the maven
release plugin takes care of it so nicely. This JIRA and PR should be closed
in my opinion.
> Use ${project.version} instead of hard-coded version in nifi-redis-bundle
> -------------------------------------------------------------------------
>
> Key: NIFI-5383
> URL: https://issues.apache.org/jira/browse/NIFI-5383
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Jan Hentschel
> Assignee: Mike Thomsen
> Priority: Trivial
> Fix For: 1.8.0
>
>
> Currently the {{nifi-redis-bundle}} module and its sub-modules use a
> hard-coded NiFi version. To make version updates easier this should be
> replaced by {{${project.version}}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
