Nope. It is [the version we are actually using](https://github.com/jclouds/jclouds-karaf/blob/522e245582acb3595144f4b02208909e3b935564/pom.xml#L206-L207) and it still presents the issue.
The issue is that the [jsch-agent-proxy-core](https://github.com/ymnk/jsch-agent-proxy/tree/master/jsch-agent-proxy-core/src/main/java/com/jcraft/jsch/agentproxy) classes and the [jsch-agent-proxy-jsch](https://github.com/ymnk/jsch-agent-proxy/tree/master/jsch-agent-proxy-jsch/src/main/java/com/jcraft/jsch/agentproxy) use the same package. Then, when the jsch-agent-proxy-jsch bundle exports [this](https://github.com/apache/servicemix-bundles/blob/master/jsch-agentproxy-jsch-0.0.9/pom.xml#L43), it is exporting the jsch classes, but also the core classes, which are already exported by the core bundle. The ideal solution IMO would be to change the package for the jsch classes, but it is not likely that we'll have a release soon for that (given the experience from https://github.com/ymnk/jsch-agent-proxy/issues/28). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-karaf/commit/522e245582acb3595144f4b02208909e3b935564#commitcomment-20373896
