exceptionfactory edited a comment on pull request #4779: URL: https://github.com/apache/nifi/pull/4779#issuecomment-766962393
> Yeah true they do have a pretty broad impact. However, we have to be extremely careful about which dependencies end up in our 'all things classloader' since every subordinate classloader will be impacted. Specifically when the binary of nifi is build we need to ensure ONLY those jars we want to make/force be present on every classloader is in the lib folder. We have to be careful to ensure we dont grow that as each time we do we reduce the classloader isolation nars can offer. @joewitt That makes sense. For clarification, are you suggesting any changes to the dependency management adjustments in this PR? The dependency management restructuring does not alter the class path and library directory contents, it just moves the version number management to the root Maven configuration. Both before and after these proposed changes, any extensions that leverage Bouncy Castle and also depend on `nifi-security-utils` directly or indirectly should be using the same version to avoid unexpected runtime behavior. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
