Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-5163

Confusing tab completion for adding a module dependencies

    XMLWordPrintable

Details

    • Bug
    • Status: Verified (View Workflow)
    • Major
    • Resolution: Done
    • 7.0.0.GA
    • 7.1.0.DR6
    • CLI
    • None

    Description

      Using tab completion for adding a module dependencies with module add command could lead to invalid module.xml as CLI prompt user to use module name with "system.layers.base" prefix, which is not a part of module name.

      reproduce
      Add a new module via module add command, use tab-completion for dependencies

      module add --name=<name> --resources=<path_to_jar> --dependencies=<TAB>
      module add --name=<name> --resources=<path_to_jar> --dependencies=system.<TAB>
      module add --name=<name> --resources=<path_to_jar> --dependencies=system.layers.<TAB>
      module add --name=<name> --resources=<path_to_jar> --dependencies=system.layers.base.<TAB>
      asm  ch  com  gnu  ibm  io  javaee  javax  net  nu  org  sun 
      

      this way something like following is generated in module.xml file

      <dependencies>
          <module name="system.layers.base.org.jboss.as.controller"/>
      </dependencies>
      

      however correct module name is org.jboss.as.controller

      Attachments

        Issue Links

          Activity

            People

              spyrkob Bartosz Spyrko-Smietanko
              pkremens@redhat.com Petr Kremensky (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: