[
https://issues.apache.org/jira/browse/KARAF-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831316#comment-13831316
]
Jean-Baptiste Onofré commented on KARAF-2509:
---------------------------------------------
Actually, I don't see a right way to fix that. For instance, when an user types
a command like ssh, how Karaf can know if it means ssh subshell or ssh global
scoped or alias ?
Right now, the subshell action preceed and I think it makes sense. I will
update the migration guide to invite the users to use the full qualified
command name (ssh:ssh) for the commands with the same name as a subshell.
> subshell interferes the execution of a command with the same name as the scope
> ------------------------------------------------------------------------------
>
> Key: KARAF-2509
> URL: https://issues.apache.org/jira/browse/KARAF-2509
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.0
>
>
> When a command has the same name as the scope/subshell (for install log:log
> or ssh:ssh), the subshell interferes the command execution.
> If you use the "full qualified" command name (like log:log), it works fine.
> However, when we are in the log subshell, and execute log, it's the subshell
> switch command which is executed instead of the command local to the subshell.
> To fix that, it's required some improvements in the commands NamespaceHandler.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
