Re: [jclouds/jclouds-site] Javadoc index in reverse order and link to PonyMail (#192)

2016-12-09 Thread Andrew Phillips
demobox commented on this pull request.



> @@ -8,6 +8,7 @@ title: Get in touch!
 We'd love to have your feedback, suggestions, and will be happy to help 
with anything you need. Just get in touch!
 
 
+  https://lists.apache.org/list.html?jclouds.apache.org;>Browse and 
participate in our mailing lists

For me, this link defaults to `dev@`, for some reason (alphabetical order)? Is 
that what we want?

![image](https://cloud.githubusercontent.com/assets/223702/21071458/bd495f5c-be6e-11e6-8060-093d4509a4a5.png)


>  * [2.0.x](/reference/javadoc/2.0.x/)
+* [1.9.x](/reference/javadoc/1.9.x/)
+* [1.8.x](/reference/javadoc/1.8.x/)
+* [1.7.x](/reference/javadoc/1.7.x/)

Nice!

-- 
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-site/pull/192#pullrequestreview-12342500

Re: [jclouds/jclouds-site] Javadoc index in reverse order and link to PonyMail (#192)

2016-12-09 Thread jclouds-commentator
  Go to 
http://50d0c57bec39f04aaa32-5733c3472e65647debd31c25780fa066.r14.cf5.rackcdn.com/
 to review your changes.

-- 
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-site/pull/192#issuecomment-266072172

[jclouds/jclouds-site] Javadoc index in reverse order and link to PonyMail (#192)

2016-12-09 Thread Ignasi Barrera

You can view, comment on, or merge this pull request online at:

  https://github.com/jclouds/jclouds-site/pull/192

-- Commit Summary --

  * Javadoc index in reverse order and link to PonyMail

-- File Changes --

M community/index.md (1)
M reference/javadoc/index.md (6)

-- Patch Links --

https://github.com/jclouds/jclouds-site/pull/192.patch
https://github.com/jclouds/jclouds-site/pull/192.diff

-- 
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-site/pull/192


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

2016-12-09 Thread ASF GitHub Bot (JIRA)

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