[
https://issues.apache.org/jira/browse/NIFI-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964574#comment-15964574
]
Joseph Witt commented on NIFI-3690:
-----------------------------------
[~jameswing] i am ok with you pulling it out. However, the JSON thing is easy
to workaround ( i believe) because we will do a binary exclusion of the
offending artifact and pull in a new cleanroom one that should work.
As for the other dependencies yes we need to make sure the binary artifact L&N
of the nar itself (and if anything needing rollup) is covered. There are a
very large number of dependencies in here. Not sure if all are L&N friendly or
not but we need to check every one of them and update the L&N as appropriate.
If you decide to pull it out for now so that can get done on a less tight
timeline we'll be good that way too.
Thanks
Joe
> 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)
