[
https://issues.apache.org/jira/browse/NIFI-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412902#comment-15412902
]
ASF subversion and git services commented on NIFI-2026:
-------------------------------------------------------
Commit cb76e67a3dc3f54917f1bc4629250ac1b3ecf1ea in nifi's branch
refs/heads/master from [~mattyb149]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=cb76e67 ]
NIFI-2026 This closes #812. Moved vendor repositories into Maven profiles
> nifi-hadoop-libraries-nar should use profiles to point to different hadoop
> distro artifacts
> -------------------------------------------------------------------------------------------
>
> Key: NIFI-2026
> URL: https://issues.apache.org/jira/browse/NIFI-2026
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Andre
> Assignee: Andre
> Fix For: 1.0.0
>
>
> Raising a JIRA issue as discussed with [~mattyb149] as part of PR-475.
> Users using particular Hadoop versions may struggle to use *HDFS against a
> cluster running proprietary or particular versions of HDFS.
> Therefore, until we find a cleaner way of BYO hadoop machanism (as suggested
> in NIFI-710), we should consider introducing a maven profiles to support
> different hadoop library, enabling users to compile.
> This should cause no changes to default behaviour, just eliminating the need
> to clone, modify, build and copy NAR bundles over standard NiFi artifacts.
> Unless the profile is explicitly requested, build will still includes just
> the Apache licensed artifacts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
