Github user olegz commented on the issue:
https://github.com/apache/nifi/pull/1156
@bbende I now tend to agree. Per-lifecycle class loading is an edge case
and we only use it right now in SpringContextProcessor where it is required due
to the fact that Spring itself is a developer framework and it's class path
heavily depends on volatile artifacts (e.g., configuration files, application
code etc.). So while most JARs will remain the same, the overall classpath may
change after re-starts. For the cases where one deals with JMS
ConectionFactories and JDBS Drivers that most likely never be the case.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
