[
https://issues.apache.org/jira/browse/NIFI-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412289#comment-15412289
]
Joseph Witt commented on NIFI-2026:
-----------------------------------
[~mattyb149] I recommend commenting the profile definition for '-PvendorRepos'
to say something to the effect of
"This profile is here as a convenience for folks that want to build against
vendor specific distributions of the various Hadoop ecosystem libraries. These
will alter which dependencies are sourced in a manner that can adjust the
correct LICENSE and NOTICE requirements for any affected jar and the resulting
assembly overall. These L&N impacts are not automatically handled by the build
process and are the responsibility of those creating and using the resulting
binary artifacts."
> 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)
