[GitHub] nifi issue #3040: NIFI-5648: Enable to launch NiFi and ignore the failed ext...

2018-10-08 Thread bbende
Github user bbende commented on the issue: https://github.com/apache/nifi/pull/3040 I agree with the points made by @joewitt , although this PR did make me compare what we are doing for processors vs. controller services... I noticed that for processors the try/catch wraps th

[GitHub] nifi issue #3040: NIFI-5648: Enable to launch NiFi and ignore the failed ext...

2018-10-06 Thread kemixkoo
Github user kemixkoo commented on the issue: https://github.com/apache/nifi/pull/3040 Yes, I see. If can to manage the extensions dynamically, should be better, but need more refactor, so I just do a simple fix to load instance well. ---

[GitHub] nifi issue #3040: NIFI-5648: Enable to launch NiFi and ignore the failed ext...

2018-10-02 Thread joewitt
Github user joewitt commented on the issue: https://github.com/apache/nifi/pull/3040 @kemixkoo I can understand where the desire for this comes from but I think this is a dangerous approach. Fundamentally we're saying that we know at startup time there is a classpath issue. Continui