You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Ignasi Barrera (JIRA)" <ji...@apache.org> on 2017/01/05 14:38:58 UTC

[jira] [Commented] (JCLOUDS-1221) features should come from jclouds/jclouds only?

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

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

I think it can provide value to have providers in labs there. It is good, for example, to have Azure there.
The CLI is a very easy and convenient way to quickly test providers, and having them in the CLI early provides value IMO.

Perhaps an intermediate approach would be to rename the features for the labs providers to display (LABS) or something that properly qualifies them, so users that install them know what they are doing?

> 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)