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:31:00 UTC

[jira] [Closed] (JCLOUDS-855) JClouds Karaf on Windows

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

Andrew Gaul closed JCLOUDS-855.
-------------------------------
    Resolution: Won't Fix

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

> JClouds Karaf on Windows
> ------------------------
>
>                 Key: JCLOUDS-855
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-855
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-karaf
>    Affects Versions: 1.7.3, 1.8.1
>         Environment: Karaf 2.4.1 on Windows 7
>            Reporter: Alexander Grzesik
>            Priority: Major
>         Attachments: jclouds-karaf.txt
>
>
> Due to the integration of ssh via com.jcraft.jsch in Jclouds 1.7, the karaf feature is no longer working on windows. When trying to create a (aws-ec2) computing service you get the exception you see attached.
> The problem seems that on windows the com.jcraft.jsch.agentproxy tries to lookup some classes specific to the win32 implementation.
> On a Linux system with karaf 2.4.1, jclouds works correctly.
> Jclouds 1.6.3 and karaf 2.4.1 works without problems on windows, too.
> Either you should provide in your karaf feature the necessary additional bundles for the windows com.jcraft.jsch.agentproxy or at least make the ssh agent not break the complete functionality as it is optional to use as I understand.



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