> We have already the default engine jars in the classpath, and if we throw an > exception users won't be able to workaround it.
Given that, as you say, we _should_ have valid scripting engines on the classpath, if we are not able to load those in the OSGi environment I would consider that something like a "fatal error" and would be tempted to blow up. In other words, I can't see any reason why this should be transient, and if it's broken I'd say it's something I'd rather have a JIRA ticket for. Does that make some kind of sense? -- 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-245183901
