Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2768
@peter-toth Since this is adding a new dependency (at least directly and
possibly transitively) we'll at least need to make a License and Notice update.
Can you please verify what the old dependencies that would be included are for
impacted nar(s) and see what the difference is. The new artifacts need to be
in the Nar(s) L&N as appropriate. For commons-text at least I suspect we need
an entry in the spark-nar and possibly in the nifi-assembly notice as well.
Please take a look to identify the gaps so we can get this included.
To the other comment(s) from otto/marco it would be good, if there is
already a unit test, to create one which shows this change. If there were not
unit or integration tests I dont think you should be held to a higher standard
than the original author was while you're trying to fix a bug. We can proceed
without if so but we cannot proceed without L&N updates as needed.
---
