Great! Would it make sense to keep this anyway as a sane fallback, or should we replace it by a runtime exception? Silently returning null is not OK.
We have already the default engine jars in the classpath, and if we throw an exception users won't be able to workaround it. I'd say that even with your patch it makes sense to keep this fallback. WDYT? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-karaf/pull/78#issuecomment-245183163
