[JCLOUDS-1199] jclouds-cli throws NPE in compute list commands

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: jclouds-cli
• Assignee: Ignasi Barrera
• Reporter: Ignasi Barrera
• Created: 09/Nov/16 16:02
• Updated: 11/Nov/16 10:12
• Resolved: 11/Nov/16 10:12

Description

In this commit in jclouds-karaf we changed the way in which the ScriptEngineManager was loaded.

Before that commit, the script engine manager was hardcoded to an instance that did not work properly in OSGI environments, so we changed the way it was initialised to let it be injected the right instance.

While this works well in Karaf, this breaks the jclouds-cli when not using the interactive mode. When using the shell script, the CLI directly creates the Command instances, and those instances are now missing the ScriptEngineManager object, resulting in the mentioned NPE.

My proposed fix would be to manually set the new ScriptEngineManager() in the CLI, just after creating the command. This way the CLI keeps the legacy behavior while we don't couple jclouds-karaf to a script engine that does not work well in OSGi environments.

Issue Links

• links to: jclouds-cli PR #35: Fix the script engine in the jclouds CLI