[
https://issues.apache.org/jira/browse/NIFI-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091201#comment-15091201
]
ASF subversion and git services commented on NIFI-1347:
-------------------------------------------------------
Commit fddb4cd52a218434e8ff3e137cd6a12add3274c9 in nifi's branch
refs/heads/master from [~joewitt]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=fddb4cd ]
NIFI-1347 Updated to use explicit version reference
Signed-off-by: joewitt <[email protected]>
> 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)
