-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR3
-
None
In standalone mode of jboss-cli, the command: 'deployment-info --headers' throws Java exceptions instead of a proper problem description.
[standalone@localhost:9990 /] deployment-info --headers Failed to perform operation: java.util.concurrent.ExecutionException: Operation failed: Operation failed: java.lang.IllegalArgumentException:null
Example:
[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
Steps to reproduce:
Standalone:
[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 /]
- clones
-
WFCORE-1739 CLI 'deployment-info --headers' throws errors in standalone mode
- Resolved
- is cloned by
-
JBEAP-5755 (7.0.z) CLI 'deployment-info --headers' throws errors in standalone mode
- Closed
- is incorporated by
-
JBEAP-6068 (7.1.0) Upgrade to WildFly Core 3.0.0.Alpha9
- Closed
- is related to
-
WFCORE-1876 Content completion does not work for deployment-info --headers
- Resolved
-
JBEAP-6496 (7.1.0) Content completion does not work for deployment-info --headers
- Closed