Description of problem: CLI should error out gracefully with an error message rather than blowing up if the required scripting libraries are not available Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. on an rhq-server machine which doesn't have the java script library 2.go to the cli/target/rhq-remoting-cli-1.4.0-SNAPSHOT/bin directory 3. run ./rhq-cli.sh Actual results: [root@10-16-120-159 bin]# ./rhq-cli.sh Exception in thread "main" java.lang.NullPointerException at org.rhq.enterprise.client.commands.ScriptCommand.<init>(ScriptCommand.java:83) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at org.rhq.enterprise.client.ClientMain.initCommands(ClientMain.java:118) at org.rhq.enterprise.client.ClientMain.main(ClientMain.java:103) Expected results: error message Additional info:
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
jsanda - is this even an issue anymore (since we don't support jdk5)