[jboss-jira] [JBoss JIRA] (WFCORE-1878) CLI should not rely on values that could conflict with shell operators

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13309300#comment-13309300 ] 

Brian Stansberry commented on WFCORE-1878:
------------------------------------------

IIRC <ALL> is new and has never been in a .Final release, so if there is any concern about it let's change it now. You can increase the priority to Critical or Blocker and set a Fix Version if that's your plan. That will help ensure it doesn't get missed.

> 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)