You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/10/19 09:28:58 UTC

[jira] [Commented] (KARAF-2454) Portable way to make custom shell commands (without inheriting from OsgiCommandSupport)

    [ https://issues.apache.org/jira/browse/KARAF-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15588173#comment-15588173 ] 

ASF subversion and git services commented on KARAF-2454:
--------------------------------------------------------

Commit f1dd4a94c8d3cd05ca35513256e9e787dffc42c9 in karaf's branch refs/heads/master from [~gnt]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=f1dd4a9 ]

[KARAF-397] Allow completion of non Karaf based osgi commands
[KARAF-2454] Portable way to make custom shell commands

Leverage more of the gogo-jline bundle, such as builtin commands, completion mechanism.
Remove duplicate commands from Karaf (which has the benefit of making sure all builtin commands are available when the session is created, so when the initialization script runs).

> Portable way to make custom shell commands (without inheriting from OsgiCommandSupport)
> ---------------------------------------------------------------------------------------
>
>                 Key: KARAF-2454
>                 URL: https://issues.apache.org/jira/browse/KARAF-2454
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-shell
>    Affects Versions: 2.3.2
>         Environment: All
>            Reporter: Morten Christensen
>            Assignee: Guillaume Nodet
>             Fix For: 4.1.0
>
>
> I would like to be able to create osgi shell commands that work across karaf and standard osgi implementations like felix, eclipse (both using gogo). When deployed in karaf, the shell commands should support completion and the other karaf specific features and when deployed in plain felix just work as in the standard. Currently, karaf makes this difficult as commands must extend from karaf specific OsgiCommandSupport class. I would like a way to support karaf using some karaf specific configuration outside the command classes that should use standard OSGI stuff only. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)