[jboss-jira] [JBoss JIRA] (WFCORE-854) CLI Variables 'set' command broken

[Joe Wertz (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Wertz updated WFCORE-854:
-----------------------------
    Description: 
Before AESH had 'export', added by the AESH upgrade, the CLI created 'set' to handle variables.

With the upgrade, the commands overlap and interfere.

Using commands, 'set name=value', and then 'echo $name', AESH will now search it's 'export' list for the variable. Which doesn't exist, so the variable is replaced with nothing. By the time the input processing gets to the CLI to search the 'set' variable list, the '$name' part of the string has been removed from the line by AESH's export processing.

Export didn't exist before the upgrade, so disabling it doesn't cause problems.

This was missed by the tests because part of the CLI actually bypasses AESH and most of the tests use that method.

  was:
Before AESH had 'export', added by the AESH upgrade, the CLI created 'set' to handle variables.

With the upgrade, the commands overlap and interfere.

Using commands, 'set name=value', and then 'echo $name', AESH will now search it's 'export' list for the variable. Which doesn't exist, so the variable is replaced with nothing. By the time the input processing gets to the CLI to search the 'set' variable list, the '$name' part of the string has been removed from the line by AESH's export processing.

Export didn't exist before the upgrade, so disabling it doesn't cause problems.



> CLI Variables 'set' command broken
> ----------------------------------
>
>                 Key: WFCORE-854
>                 URL: https://issues.jboss.org/browse/WFCORE-854
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 2.0.0.Alpha12
>            Reporter: Joe Wertz
>            Assignee: Joe Wertz
>             Fix For: 2.0.0.Alpha12
>
>   Original Estimate: 2 hours
>          Time Spent: 2 hours
>  Remaining Estimate: 0 minutes
>
> Before AESH had 'export', added by the AESH upgrade, the CLI created 'set' to handle variables.
> With the upgrade, the commands overlap and interfere.
> Using commands, 'set name=value', and then 'echo $name', AESH will now search it's 'export' list for the variable. Which doesn't exist, so the variable is replaced with nothing. By the time the input processing gets to the CLI to search the 'set' variable list, the '$name' part of the string has been removed from the line by AESH's export processing.
> Export didn't exist before the upgrade, so disabling it doesn't cause problems.
> This was missed by the tests because part of the CLI actually bypasses AESH and most of the tests use that method.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)