[jboss-jira] [JBoss JIRA] (WFCORE-1878) CLI should not rely on values that could conflict with shell operators
Brian Stansberry (JIRA)
issues at jboss.org
Wed Oct 19 09:30:00 EDT 2016
[ https://issues.jboss.org/browse/WFCORE-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13309310#comment-13309310 ]
Brian Stansberry commented on WFCORE-1878:
------------------------------------------
I recommend starting with pinging the QE Tester on the feature to get quick input on your plans. Then comment on EAP7-515, update the analysis doc, the code and the community docs.
> 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
> Priority: Blocker
> Fix For: 3.0.0.Alpha10
>
>
> 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)
More information about the jboss-jira
mailing list