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

Content completion does not work for deployment-info --headers

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 3.0.0.Alpha11
    • None
    • CLI
    • None

    Description

      [standalone@localhost:9990 /] deployment-info --headers
      [standalone@localhost:9990 /] deployment-info --headers=<TAB><TAB>

      this does not kick in, should be:
      [standalone@localhost:9990 /] deployment-info --headers={
      after first <TAB>

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-6496 (7.1.0) Content completion does not work for deployment-info --headers

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-5710 (7.1.0) CLI 'deployment-info --headers' throws errors in standalone mode

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              jdenise@redhat.com Jean Francois Denise
              rhn-cservice-bbaranow Bartosz Baranowski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: