Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/475
@trixpan @mattyb149 We don't need to aim to cover any or all vendors. If
someone wants to submit a patch for whatever vendor's specific distribution
they want then that is fine provided all the typical licensing and notice
considerations are adhered to. I haven't looked into MapRs licensing for the
dependent libraries we need here but if it is compatible with the proper
ASF/ASLv2 licensing then great. If not then it should not be included even as
a profile. Technically speaking we do not official release binary builds at
all. We do provide them as a convenience and we do have to ensure even those
binary builds have full valid licensing. The thing we are officially releasing
is the source release so yes we could probably 'get away with' leaving the
profile in but it seems quite avoidable. If we want to allow someone to
augment their hadoop dependent libraries with vendor specific things and we're
worried about licensing we could simply have default pure ASF dependency profi
le and then let users override the profile using their settings.xml which we
can document how to do. But, if MapR or CDH or HDP libraries are valid then
anyone can make those available.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
