Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/3007
@MikeThomsen if the nar now includes a dependency it did not previously
include then the L&N will need to be updated, if necessary, to reflect that. I
dont recall the case of jbcrypt but I dont think that is a new dependency in
nifi overall. If we have it in a L or N of a binary artifact elsewhere then
we'll want it here too. Make sense?---
