[
https://issues.apache.org/jira/browse/NIFI-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081431#comment-15081431
]
Aldrin Piri commented on NIFI-1347:
-----------------------------------
Grabbed a copy of the patch and applied to a branch on my personal fork:
https://github.com/apiri/incubator-nifi/tree/nifi-1347
Build, contrib, and tests passed:
https://travis-ci.org/apiri/incubator-nifi/jobs/100150311
Found a version of 3.2.3 and verified build locally sans tests and contrib on
OS X.
Looking through 3.2.5 release notes, looks like this may have been an issue in
3.2.5 itself, but consistency sounds good as well
Could you please add a comment for the git commit? Currently this is just the
JIRA issue and nothing else. After that +1 for me.
> Use explicit version reference and fix dependency reference
> -----------------------------------------------------------
>
> Key: NIFI-1347
> URL: https://issues.apache.org/jira/browse/NIFI-1347
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Joseph Witt
> Assignee: Joseph Witt
> Priority: Trivial
> Fix For: 0.5.0
>
> Attachments: 0001-NIFI-1347.patch
>
>
> The riemann bundle had the nifi-riemann-nar referencing a dependency using
> maven project version shortcut rather than explicit reference. We've
> abolished use of this because it has been observed to cause strange
> multi-module or release plugin related behavior and it offers no benefit.
> Versions are automatically managed during the release process and using
> version plugins as needed so not worth the hassle. Also, the dependency
> section of the bundle referenced the com.aphyr client which means each sub
> module automatically gets that dependency. Better to switch to
> dependencyManagement and then explicitly pull in the needed item on the
> appropriate artifact.
> Finally, adjusted the formatting to be more consistent with other modules.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
