[
https://issues.apache.org/jira/browse/NIFI-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964555#comment-15964555
]
James Wing commented on NIFI-3690:
----------------------------------
[~joewitt], to clarify, this ticket is about the incomplete recognition of
transitive dependencies in the nifi-gcp-nar LICENSE and NOTICE. It can be
resolved by expanding on the LICENSE and NOTICE. Is that correct?
But isn't the transitive JSON.org dependency a hard obstacle? I do not
understand what you will resolve in NIFI-3089 with a PR.
The obvious immediate resolution to both issues is to un-merge the nifi-gcp-nar
until we are comfortable with it, and so it will not constrain a 1.2.0 release.
I plan to do this unless you are looking for a different resolution.
> nifi-gcp-bundle contains undeclared (L&N) dependencies
> ------------------------------------------------------
>
> Key: NIFI-3690
> URL: https://issues.apache.org/jira/browse/NIFI-3690
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Joseph Witt
> Priority: Blocker
> Fix For: 1.2.0
>
>
> [~gene-telligentdata] [~jameswing] In working NIFI-3089 I found the
> nifi-gcp-nar. It contained a transitive dependency on org.json library which
> is Category X for apache so must be removed. I've got that address in
> NIFI-3089 and will have a PR for that soon.
> However, in looking at the L&N for the nar itself there are a ton of
> dependencies in the nar and they're not referenced in the nar's L&N. We must
> resolve this before nifi-gcp-nar can be released w/NiFi.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
