Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-854

CLI Variables 'set' command broken

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.0.0.Alpha13
    • 2.0.0.Alpha12
    • CLI
    • None

      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.

            gonthim Joe Wertz (Inactive)
            gonthim Joe Wertz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 2 hours
                2h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 hours
                2h