Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/1156
@olegz I pushed up a second commit that with the change that I described
above, and also some of the changes from your feedback. Unfortunately I had
already rebased my branch before you had started reviewing, so i ended up
having to force push, but I left it as two commits where the first one has the
stuff you already looked at, and the second commit has changes after that.
I think the remaining discussion point is mostly around how restrictive we
get regarding what happens when one or more resources can't be found. I
understand the point about what happens if something that is necessary can't be
loaded, but I also want to give flexibility to the developers using this
feature. There may be cases where someone wants to provide a couple of
directories that are common locations for a given library, and if found then
load whatever is found, but if not then maybe they don't care. One option might
be to provide a validator that uses ClassLoader.getURLsforClasspath to validate
everything resolves, and then document that this is available, but not enforce
that it is always used.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
