[jboss-jira] [JBoss JIRA] (WFCORE-1739) CLI 'deployment-info --headers' throws errors in standalone mode

CLI 'deployment-info --headers' throws errors in standalone mode ---------------------------------------------------------------- Key: WFCORE-1739 URL: https://issues.jboss.org/browse/WFCORE-1739 Project: WildFly Core Issue Type: Bug Reporter: Bartosz Baranowski Assignee: Bartosz Baranowski In standalone mode of jboss-cli, the command: 'deployment-info --headers' throws Java exceptions instead of a proper problem description. {code:bash} [standalone@localhost:9990 /] deployment-info --headers Failed to perform operation: java.util.concurrent.ExecutionException: Operation failed: Operation failed: java.lang.IllegalArgumentException:null {code} Tab complete does not work beyond '--headers=' and starts working again after '\{' is typed. *Example*: {code:bash} [standalone@localhost:9990 /] deployment-info --headers<TAB>=<TAB><TAB> Failed to handle 'deployment-info --headers=': newValue is null [standalone@localhost:9990 /] deployment-info --headers={<TAB> allow-resource-service-restart rollback-on-runtime-failure blocking-timeout rollout {code} *Steps to reproduce*: Standalone: {code:bash} [standalone@localhost:9990 /] deployment-info --headers Failed to perform operation: java.util.concurrent.ExecutionException: Operation failed: Operation failed: java.lang.IllegalArgumentException:null [standalone@localhost:9990 /] deployment-info --headers=<TAB><TAB> Failed to handle 'deployment-info --headers=': newValue is null [standalone@localhost:9990 /] deployment-info --headers={} NAME RUNTIME-NAME PERSISTENT ENABLED STATUS jboss-kitchensink-ml-ear.ear jboss-kitchensink-ml-ear.ear true false STOPPED jboss-kitchensink.war jboss-kitchensink.war true false STOPPED jboss-modules.jar jboss-modules.jar true false STOPPED {code}