jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignasi Barrera (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-1221) features should come from jclouds/jclouds only?
Date Thu, 05 Jan 2017 15:24:58 GMT

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

Ignasi Barrera commented on JCLOUDS-1221:
-----------------------------------------

IIRC that feature allows to create the reusable comptue/blobstore services, and let usres
persist them so they can be easily referenced: https://github.com/jclouds/jclouds-karaf#using-multiple-services-per-providerapi

{quote}
Also I think we should expose the jclouds-drivers as OSGi feature
{quote}

I'm not a karaf expert :) How would it help users having the drivers exposed as standalone
features?

> features should come from jclouds/jclouds only?
> -----------------------------------------------
>
>                 Key: JCLOUDS-1221
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1221
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-karaf
>            Reporter: Andrea Turli
>            Priority: Minor
>
> I'm trying to update the feature.xml file in jclouds-karaf and I've notice that there
are feature that reference bundles coming from `mvn:org.apache.jclouds.labs` 
> As per the nature of jclouds-labs project, some providers may also never be promoted
so I'm not sure jclouds-karaf should reference them. This make the jclouds-karaf maintenance
complicated IMHO



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

Mime
View raw message