Brian Stansberry created WFLY-2224: -------------------------------------- Summary: CLI doesn't exit batch mode when failures occur in run-batch Key: WFLY-2224 URL: https://issues.jboss.org/browse/WFLY-2224 Project: WildFly Issue Type: Bug Components: CLI Affects Versions: 8.0.0.Beta1 Reporter: Brian Stansberry Assignee: Alexey Loubyansky Fix For: 8.0.0.CR1 If you execute a batch that fails, the CLI remains in batch mode. [domain@localhost:9990 /] batch [domain@localhost:9990 / #] /profile=test:add #1 /profile=test:add [domain@localhost:9990 / #] :bogus #2 /:bogus [domain@localhost:9990 / #] run-batch JBAS014884: No operation named 'bogus' exists at address [] [domain@localhost:9990 / #] This might be intentional (e.g. to let me fix a typo in my ":bogus" op), but if so, perhaps some output explaining that would be good? And for non-interactive mode staying in the batch seems wrong. The same problem occurs in the EAP branch, which is where I first noticed it when investigating another issue. In that case the :bogus command wasn't bogus but was a proper op that failed for legitimate reasons. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira