[
https://issues.jboss.org/browse/WFCORE-1878?page=com.atlassian.jira.plugi...
]
Jean-Francois Denise edited comment on WFCORE-1878 at 10/19/16 9:26 AM:
------------------------------------------------------------------------
Yes, that is the plan. I am wandering what is the impact on the original RFE:
https://issues.jboss.org/browse/EAP7-515
Should I move it back to Analysis dev? Should we keep it as it is and simply change the
public community documentation?
was (Author: jdenise):
Yes, that is the plan. I am wandering what is the impact on the original RFE:
https://issues.jboss.org/browse/EAP7-515
Should I move it back to Analysis dev? Should be keep it as it and simply change the
public community documentation?
CLI should not rely on values that could conflict with shell
operators
----------------------------------------------------------------------
Key: WFCORE-1878
URL:
https://issues.jboss.org/browse/WFCORE-1878
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
If we move to a new CLI implementation that relies on Aesh Command parsing, then we will
need to activate Aesh operator parsing to handle the following case: ls -l >
output.txt
Today, the deploy command makes use of <ALL> as a well known value to refer to all
disabled deployment items. This will conflict with Aesh parser.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)