You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Gaul (Jira)" <ji...@apache.org> on 2020/09/26 02:32:00 UTC

[jira] [Closed] (JCLOUDS-84) Separate OSGi aware from non-OSGi aware commands

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

Andrew Gaul closed JCLOUDS-84.
------------------------------
    Resolution: Fixed

The Karaf project now maintains the jclouds bindings; please open an issue there.

> Separate OSGi aware from non-OSGi aware commands
> ------------------------------------------------
>
>                 Key: JCLOUDS-84
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-84
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-cli, jclouds-karaf
>            Reporter: Ioannis Canellos
>            Priority: Major
>
> While reviewing JCLOUDS-71 I realized that is not crystal clear which of commands are OSGi aware and which are non-OSGi aware. This is causing a lot of confusion and should be addressed.
> So, most of the commands can be run both inside and outside OSGi (there are a couple of OSGi only commands). The fact that all commands inherit from Compute/BlobStoreCommandBase which contains OSGi specific properties make this very confusing. We should break the BaseCommands into something that makes it very clear if the command is OSGi specific or not. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)