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 2016/01/25 12:44:39 UTC

[jira] [Resolved] (JCLOUDS-1051) Depedency on com.hierynomus.ssh breaks jclouds-karaf

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

Ignasi Barrera resolved JCLOUDS-1051.
-------------------------------------
    Resolution: Fixed

> Depedency on com.hierynomus.ssh breaks jclouds-karaf
> ----------------------------------------------------
>
>                 Key: JCLOUDS-1051
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1051
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-karaf
>    Affects Versions: 2.0.0
>            Reporter: Andrew Gaul
>            Assignee: Ignasi Barrera
>            Priority: Blocker
>             Fix For: 2.0.0
>
>
> The changes introduced in [pull request 841|https://github.com/jclouds/jclouds/pull/841] upgrade the SSHJ dependency and break jclouds-karaf.
> SSHJ has changed its maven coordinates from {{net.schmizz}} to {{com.hierynomus}}. Our jclouds-karaf integration relied on existing bundles for that dependency, but the latest bundle available for the {{org.apache.servicemix.bundles.jsch-agentproxy-sshj}} still uses the old package.
> Since there is no bundle available that uses the new SSHJ Maven dependency, jclouds-karaf is broken.
> There are several approaches to fix this:
> * Provide our own agentproxy bundle with the right SSHJ dependency.
> * Package the agentproxy class (it is just only one class) as part of the jclouds SSH driver. License is [compatible|http://www.apache.org/legal/resolved.html#category-a], as it is a BSD 3-clause.
> * Change jclouds-karaf to use the JSCH ssh driver.
> Until there is no bundle available, we should try to move jclouds-karaf to use jsch.



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