[
https://issues.jboss.org/browse/WFCORE-1657?page=com.atlassian.jira.plugi...
]
Bartosz Spyrko-Śmietanko moved JBEAP-5221 to WFCORE-1657:
---------------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1657 (was: JBEAP-5221)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: CLI
(was: CLI)
Affects Version/s: 2.2.0.CR7
3.0.0.Alpha3
(was: 7.0.0.GA)
Confusing tab completion for adding a module dependencies
---------------------------------------------------------
Key: WFCORE-1657
URL:
https://issues.jboss.org/browse/WFCORE-1657
Project: WildFly Core
Issue Type: Bug
Components: CLI
Affects Versions: 2.2.0.CR7, 3.0.0.Alpha3
Reporter: Bartosz Spyrko-Śmietanko
Assignee: Bartosz Spyrko-Śmietanko
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
{noformat}
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
{noformat}
this way something like following is generated in module.xml file
{code:xml}
<dependencies>
<module name="system.layers.base.org.jboss.as.controller"/>
</dependencies>
{code}
however correct module name is {{org.jboss.as.controller}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)