[jira] [Commented] (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:comment-tabpanel=15735662#comment-15735662
]
ASF GitHub Bot commented on JCLOUDS-1051:
-
Github user andreaturli commented on the issue:
https://github.com/apache/brooklyn-server/pull/481
FYI looks like `jclouds-karaf` project is already dealing with sshj problem
those are the 2 relevant discussions
https://issues.apache.org/jira/browse/JCLOUDS-1051
https://issues.apache.org/jira/browse/JCLOUDS-1156
I think `jclouds-karaf` is ready to switch back to sshj — see
https://github.com/jclouds/jclouds-karaf/pull/77#issuecomment-244902646 and
this will help long-term, I think.
> 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)
[jira] [Commented] (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:comment-tabpanel=15115073#comment-15115073
]
ASF subversion and git services commented on JCLOUDS-1051:
--
Commit 73b61fc28cb613851b261670bd0599b66aae66f0 in jclouds-karaf's branch
refs/heads/master from [~nacx]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-karaf.git;h=73b61fc ]
JCLOUDS-1051: Fix SSH dependencies and remove obsolete providers
> 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)
[jira] [Commented] (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:comment-tabpanel=15112225#comment-15112225
]
Ignasi Barrera commented on JCLOUDS-1051:
-
I have already fixed this in my fork by changing jclouds-karaf to JSCH. See the
following commit:
https://github.com/nacx/jclouds-karaf/commit/22d63ad77426e85f06b19a92c776fc8ba3cef85f
[~ccustine], [~iocanel], [~andrewp], could you have a look and validate this
change?
I can't open a pull request yet as it depends on the following PR (I used the
same commit to also remove unexisting providers and add some missing ones):
https://github.com/jclouds/jclouds/pull/904
> 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 really only one class) as part of the
> jclouds SSH driver. Licenses 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)
[jira] [Commented] (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:comment-tabpanel=15112419#comment-15112419
]
Ignasi Barrera commented on JCLOUDS-1051:
-
PR here: https://github.com/jclouds/jclouds-karaf/pull/72
> 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)
[jira] [Commented] (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:comment-tabpanel=15112488#comment-15112488
]
Ignasi Barrera commented on JCLOUDS-1051:
-
Great! There is a small bit still failing in my PR, but just related to the GCE
addition. I'm fixing it now, btw!
> 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)
[jira] [Commented] (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:comment-tabpanel=15112482#comment-15112482
]
Andrew Phillips commented on JCLOUDS-1051:
--
> Until there is no bundle available, we should try to move jclouds-karaf to
> use jsch.
+1 to that. I've just asked the jsch-agent-proxy maintainer whether it would be
possible to create a new version that updates the dependency, so we can ask the
ServiceMix team to create a bundle for it:
https://github.com/ymnk/jsch-agent-proxy/issues/28
> 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)
