You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "james strachan (JIRA)" <ji...@apache.org> on 2010/09/15 16:06:33 UTC

[jira] Updated: (KARAF-154) allow @Command objects to implement Runnable - or have a @Run annotation on the method so that they don't have to extend Action to avoid runtime Karaf dependency

     [ https://issues.apache.org/jira/browse/KARAF-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

james strachan updated KARAF-154:
---------------------------------

    Fix Version/s: 2.2.0
                       (was: 2.1.0)
         Priority: Minor  (was: Major)

more of a future enhancement, lets defer it

> allow @Command objects to implement Runnable - or have a @Run annotation on the method so that they don't have to extend Action to avoid runtime Karaf dependency
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KARAF-154
>                 URL: https://issues.apache.org/jira/browse/KARAF-154
>             Project: Karaf
>          Issue Type: Improvement
>          Components: console
>            Reporter: james strachan
>            Priority: Minor
>             Fix For: 2.2.0
>
>
> It would be nice to be able to write commands using either the JDK's Runnable interface, or to use a @Run annotation (or @Execute or something) to mark the method which should be invoked when the command is run. 
> This would mean that the only dependency on Karaf for writing commands would be annotations; so there would be no runtime class dependency; letting us embed karaf commands all over the place without folks worrying about adding another runtime dependency to their code

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.