[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968311#comment-13968311
]
Andrew Phillips commented on JCLOUDS-427:
-
> If a 1.6.4 release is not planned why does this issue have it marked as such
> in its "Fixed Version/s"
> field?
Fair point. I suspect it was set because the issue should be resolved in the
current 1.6.x branch, the next release of which would be 1.6.4. Similarly,
1.8.0 has not been released yet, but that will be the version in which the
issue will be fixed on trunk.
If you cannot upgrade to Guava 16 to use jclouds 1.7.1, could you send an email
to the user list [1] to help us gauge how many users are in a similar
situation? That will make it easier to decide on the priority of a 1.6.4
release.
Thanks!
[1] http://jclouds.apache.org/community/
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967994#comment-13967994
]
Ishaaq Chandy commented on JCLOUDS-427:
---
If a 1.6.4 release is not planned why does this issue have it marked as such in
its "Fixed Version/s" field? I ask because, for many convoluted reasons (jar
dependency hell), it isn't actually possible for us to upgrade to Guava 16.x
right now.
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967199#comment-13967199
]
ASF subversion and git services commented on JCLOUDS-427:
-
Commit 6a6a45ed944824f3cf67621d7209cd2aca384960 in jclouds-karaf's branch
refs/heads/master from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-karaf.git;h=6a6a45e ]
JCLOUDS-427: Upgrading Guava 16.0 -> 16.0.1
Fixes Guava issue 1635.
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899385#comment-13899385
]
Andrew Phillips commented on JCLOUDS-427:
-
[~bmabey]: If a quick fix is OK for now, see
http://jclouds.apache.org/documentation/userguide/installation-guide/#snapshot
or http://apache.markmail.org/thread/637ayb6d6uz36bam for instructions on
getting hold of 1.6.3-SNAPSHOT.
Hope that helps!
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899362#comment-13899362
]
Ben Mabey commented on JCLOUDS-427:
---
Yeah, I'm looking for a quick fix now so I can take time to upgrade to the 1.7x
line. A 1.6.3-SNAPSHOT would work for me but I am not finding it in Maven
Central either. I'll look into making the jump to 1.7.1.
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899356#comment-13899356
]
Andrew Phillips commented on JCLOUDS-427:
-
[~bmabey]: 1.6.4 is not currently planned, as far as I'm aware. I take it from
your comment that upgrading to 1.7.1 is not an option for you. Are you able to
use 1.6.3-SNAPSHOT successfully for now (this contains the relevant workaround)?
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899337#comment-13899337
]
Ben Mabey commented on JCLOUDS-427:
---
Thanks for resolving this issue so quickly. Do you have any idea when 1.6.4
will land on Maven Central?
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898471#comment-13898471
]
Andrew Phillips commented on JCLOUDS-427:
-
1.7.1 is now available in Maven Central:
http://search.maven.org/#artifactdetails%7Corg.apache.jclouds%7Cjclouds%7C1.7.1%7Cpom
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896652#comment-13896652
]
ASF subversion and git services commented on JCLOUDS-427:
-
Commit 4c07702d29de64df45c11819c2cc9d725382b0c2 in branch refs/heads/master
from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=4c07702 ]
JCLOUDS-432: Revert "JCLOUDS-427: Avoiding Guava reflection code broken in Java
7u51"
This reverts commit 8ff60020f85ae5d9f57e9a25a6342fb7b00e1d2a.
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896650#comment-13896650
]
ASF subversion and git services commented on JCLOUDS-427:
-
Commit 02615adc4f45799d07f61727167b65c87458f573 in branch refs/heads/master
from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=02615ad ]
JCLOUDS-427: Upgrading Guava 16.0 -> 16.0.1
Fixes Guava issue 1635.
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892471#comment-13892471
]
Andrew Phillips commented on JCLOUDS-427:
-
For those following this issue: we're looking to get a 1.7.1 release that fixes
this out in the next few days.
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891375#comment-13891375
]
ASF subversion and git services commented on JCLOUDS-427:
-
Commit 9f935146dcbc52cd4f10328dbf81f499c552493e in branch
refs/heads/revert-guava-fix from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=9f93514 ]
Revert "JCLOUDS-427: Avoiding Guava reflection code broken in Java 7u51"
This reverts commit 8ff60020f85ae5d9f57e9a25a6342fb7b00e1d2a.
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891374#comment-13891374
]
ASF subversion and git services commented on JCLOUDS-427:
-
Commit e5576fce4e2bc7dd55ff1128867245d51d707835 in branch
refs/heads/revert-guava-fix from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=e5576fc ]
Upgrading Guava 16.0 -> 16.0.1
Fixes Guava issue 1635. See JCLOUDS-427
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889926#comment-13889926
]
Andrew Phillips commented on JCLOUDS-427:
-
Fixed in Guava:
https://code.google.com/p/guava-libraries/issues/detail?id=1635#c40
Yay! Patch release for Guava coming up, it seems...
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887851#comment-13887851
]
Andrew Phillips commented on JCLOUDS-427:
-
[~akozlov]: The current plan is to give the Guava team a bit more time to see
if they can fix the issue, because what we have implemented here is really a
workaround. See http://markmail.org/message/637ayb6d6uz36bam
I take it you are unable to use a recent snapshot version?
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887609#comment-13887609
]
Artem Kozlov commented on JCLOUDS-427:
--
Do you have any ETA for 1.7.1 release? This bug is really blocker and it would
be great to have this fix released.
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1, 1.6.4
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883144#comment-13883144
]
ASF subversion and git services commented on JCLOUDS-427:
-
Commit 1b2fb3e10f1863ac64a471718bc072a4792eda7e in branch refs/heads/1.6.x from
[~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=1b2fb3e ]
JCLOUDS-427: Avoiding Guava reflection code broken in Java 7u51
Backport of 8ff60020f
- Adding a version of TypeToken.where that replaces two parameters in one go
- Avoiding TypeToken type parameter replacement with wildcard bounds
Works around https://code.google.com/p/guava-libraries/issues/detail?id=1635
All reflection magic now :-(
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883087#comment-13883087
]
Andrew Gaul commented on JCLOUDS-427:
-
[~andrewp] This workaround looks good to me; thanks for fixing this! You
already committed this to master and 1.7.x and we should backport to 1.6.x.
Can you comment on the upstream Guava bug explaining your workaround?
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883007#comment-13883007
]
Andrew Phillips commented on JCLOUDS-427:
-
> updating to 1.6.4-SNAPSHOT built from the JCLOUDS-427-1.6.x branc
Thanks for confirming that, [~tom.gl]. We're planning to merge that into the
1.6.x branch soon.
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882923#comment-13882923
]
Thomas GL commented on JCLOUDS-427:
---
Just FYI, updating to 1.6.4-SNAPSHOT built from the JCLOUDS-427-1.6.x branch
(with guava 14.0.1) seems to perfectly fix the 7u51 incompatibility in our
application. Looking forward to seeing it in an official release.
Thanks for the good work.
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1
>
> Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881595#comment-13881595
]
ASF subversion and git services commented on JCLOUDS-427:
-
Commit 478e44c5ab30421cae1a40e9c375d254bd92b207 in branch
refs/heads/JCLOUDS-427-1.6.x from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=478e44c ]
JCLOUDS-427: Avoiding Guava reflection code broken in Java 7u51
Backport of 8ff60020f
- Adding a version of TypeToken.where that replaces two parameters in one go
- Avoiding TypeToken type parameter replacement with wildcard bounds
Works around https://code.google.com/p/guava-libraries/issues/detail?id=1635
All reflection magic now :-(
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1
>
> Attachments: JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881239#comment-13881239
]
Andrew Phillips commented on JCLOUDS-427:
-
[~grahamoregan]: Would a fix for 1.7.x be sufficient for you? Or are you (also)
using 1.6.x?
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1
>
> Attachments: JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881236#comment-13881236
]
Andrew Phillips commented on JCLOUDS-427:
-
Comment from [~gaul] on IRC:
[13:09] gaul: very quickly? Any urgent objections to
upgrading 1.6.x to Guava 15.0 to get the backport for the 7u51 issue to work?
[13:10] apwashere_demobo: we should *not* upgrade guava in micro
releases based on feedback from users on this issue previously
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1
>
> Attachments: JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881033#comment-13881033
]
Andrew Phillips commented on JCLOUDS-427:
-
Notified the user list about this one:
http://apache.markmail.org/thread/637ayb6d6uz36bam
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1
>
> Attachments: JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881036#comment-13881036
]
Andrew Phillips commented on JCLOUDS-427:
-
PR for 1.6.x: https://github.com/jclouds/jclouds/pull/263
Note that this requires an upgrade of Guava to 15.0, so still want to discuss
if this is feasible...
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1
>
> Attachments: JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880777#comment-13880777
]
ASF subversion and git services commented on JCLOUDS-427:
-
Commit 17c11f2b2db18dc4bcaf6c2b94bbd434810011e7 in branch
refs/heads/JCLOUDS-427-1.6.x from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=17c11f2 ]
JCLOUDS-427: Avoiding Guava reflection code broken in Java 7u51
- Adding a version of TypeToken.where that replaces two parameters in one go
- Avoiding TypeToken type parameter replacement with wildcard bounds
Works around https://code.google.com/p/guava-libraries/issues/detail?id=1635
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1
>
> Attachments: JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880765#comment-13880765
]
ASF subversion and git services commented on JCLOUDS-427:
-
Commit d3849e2ff7be939ea92e5f07cd6adb1ce1442ce9 in branch
refs/heads/JCLOUDS-427-1.6.x from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=d3849e2 ]
JCLOUDS-427: Avoiding Guava reflection code broken in Java 7u51
- Adding a version of TypeToken.where that replaces two parameters in one go
- Avoiding TypeToken type parameter replacement with wildcard bounds
Works around https://code.google.com/p/guava-libraries/issues/detail?id=1635
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0, 1.7.1
>
> Attachments: JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880747#comment-13880747
]
ASF subversion and git services commented on JCLOUDS-427:
-
Commit 597615977e7e2b10f3680aae24e541a76a1d4606 in branch refs/heads/1.7.x from
[~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=5976159 ]
JCLOUDS-427: Avoiding Guava reflection code broken in Java 7u51
- Adding a version of TypeToken.where that replaces two parameters in one go
- Avoiding TypeToken type parameter replacement with wildcard bounds
Works around https://code.google.com/p/guava-libraries/issues/detail?id=1635
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Fix For: 1.8.0
>
> Attachments: JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880708#comment-13880708
]
ASF subversion and git services commented on JCLOUDS-427:
-
Commit 8ff60020f85ae5d9f57e9a25a6342fb7b00e1d2a in branch refs/heads/master
from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=8ff6002 ]
JCLOUDS-427: Avoiding Guava reflection code broken in Java 7u51
- Adding a version of TypeToken.where that replaces two parameters in one go
- Avoiding TypeToken type parameter replacement with wildcard bounds
Works around https://code.google.com/p/guava-libraries/issues/detail?id=1635
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
> Attachments: JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880701#comment-13880701
]
ASF subversion and git services commented on JCLOUDS-427:
-
Commit 7b4d98f3cb75c0c8d199e7908bee79ee42dcb85c in branch
refs/heads/JCLOUDS-427-1.7.x from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=7b4d98f ]
JCLOUDS-427: Avoiding Guava reflection code broken in Java 7u51
- Adding a version of TypeToken.where that replaces two parameters in one go
- Avoiding TypeToken type parameter replacement with wildcard bounds
Works around https://code.google.com/p/guava-libraries/issues/detail?id=1635
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Priority: Critical
> Attachments: JCLOUDS-427.patch
>
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880453#comment-13880453
]
Andrew Phillips commented on JCLOUDS-427:
-
Squashed commit is:
https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=0c09d44b359c7d228794c51d1c78fbfc5e472aef
I'm not sure why the JIRA-Git integration doesn't seem to be working any more..?
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880447#comment-13880447
]
ASF subversion and git services commented on JCLOUDS-427:
-
Commit 0c09d44b359c7d228794c51d1c78fbfc5e472aef in branch
refs/heads/JCLOUDS-427 from [~andrewp]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=0c09d44 ]
JCLOUDS-427: Avoiding Guava reflection code broken in Java 7u51
- Adding a version of TypeToken.where that replaces two parameters in one go
- Avoiding TypeToken type parameter replacement with wildcard bounds
Works around https://code.google.com/p/guava-libraries/issues/detail?id=1635
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880131#comment-13880131
]
Andrew Phillips commented on JCLOUDS-427:
-
PR build successful! Now just for some code review...
https://github.com/jclouds/jclouds/pull/261
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879910#comment-13879910
]
Andrew Phillips commented on JCLOUDS-427:
-
> I'm guessing the type parameter replacement in ... is also failing somehow..?
Yup:
https://jclouds.ci.cloudbees.com/view/Java%207/job/jclouds-java-7u51/org.apache.jclouds$jclouds-core/16/testReport/junit/org.jclouds.internal/BaseViewTest/testUnwrapApi/
OK, done for the day. Managed to get past this one (no more test failures in
core), but still problems with the build:
https://github.com/jclouds/jclouds/pull/261
I hope someone will be able to take this further!
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879482#comment-13879482
]
Andrew Phillips commented on JCLOUDS-427:
-
Down to 1 test failure in core, and potentially more in the rest of the
codebase:
https://jclouds.ci.cloudbees.com/view/Java%207/job/jclouds-java-7u51/14/
I'm guessing the type parameter replacement in
https://github.com/jclouds/jclouds/blob/master/core/src/main/java/org/jclouds/internal/BaseView.java#L73
is also failing somehow..?
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879466#comment-13879466
]
Andrew Phillips commented on JCLOUDS-427:
-
Making some progress at
https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=shortlog;h=refs/heads/JCLOUDS-427.
It's not pretty, though ;-)
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Assignee: Andrew Phillips
>Priority: Critical
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878619#comment-13878619
]
Ignasi Barrera commented on JCLOUDS-427:
Extending a bit more my previous comment, there is the list of affected
providers:
In *1.6.x*: All providers are affected
In *1.7.x* the following providers use the RestClientModule and are affected by
the issue:
*APIS*
* atmos
* openstack-nova
* cloudsigma
* s3
* cloudservers
* swift
* keystone
* sts
* rackspace-cloudidentity
* cloudfiles
*PROVIDERS*
* aws-s3
* rackspace-cloudservers-uk
* rackspace-cloudservers-us
* azureblob
* hpcloud-objectstorage
*LABS*
* savvis-symphonyvpdc
* cloudstack-ec2
* carrenza-vcloud-director
* joyent-cloudapi
* cdmi
* vcloud-director
* azure-management
* jenkins
* greenqcloud-compute
* opsource-servers
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Priority: Critical
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878468#comment-13878468
]
Ignasi Barrera commented on JCLOUDS-427:
Just to add a note, this issue only affects the providers using the old
RestClientModule [1]. Providers that no longer provide the Async interface (and
use the HttpApiModule) are not affected.
[1]
https://github.com/jclouds/jclouds/blob/master/core/src/main/java/org/jclouds/rest/config/RestClientModule.java
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>Priority: Critical
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877503#comment-13877503
]
Mike Peachey commented on JCLOUDS-427:
--
Surely:
Critical
Crashes, loss of data, severe memory leak.
?
Completely unable to use jclouds-dependant app under JDK-7u51 - no workaround
but to downgrade Java - not always possible in shared environments and under
enforced security policies.
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875136#comment-13875136
]
Andrew Phillips commented on JCLOUDS-427:
-
Guava issue closed as a duplicate of:
https://code.google.com/p/guava-libraries/issues/detail?id=1635
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875120#comment-13875120
]
Andrew Phillips commented on JCLOUDS-427:
-
Same problem with Guava 16.0-rc1. Opened an issue against Guava:
https://code.google.com/p/guava-libraries/issues/detail?id=1637
Please vote there!
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875084#comment-13875084
]
Andrew Bayer commented on JCLOUDS-427:
--
Looks to be: https://code.google.com/p/guava-libraries/issues/detail?id=1635
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875067#comment-13875067
]
Andrew Phillips commented on JCLOUDS-427:
-
OK, Guava 15.0 bug. This:
{code}
public static TypeToken> mapOf(
TypeToken keyType, TypeToken valueType) {
return new TypeToken>() {}
.where(new TypeParameter() {}, keyType)
.where(new TypeParameter() {}, valueType);
}
{code}
(the 'where' code example in the Guava Javadoc) fails:
{code}
Printing Guava sample for 'where': java.util.Map
{code}
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875046#comment-13875046
]
Andrew Phillips commented on JCLOUDS-427:
-
OK, the second {{where}} just isn't working:
{code}
token now (step 1): org.jclouds.rest.config.SyncToAsyncHttpApiProvider
token now (after A): org.jclouds.rest.config.SyncToAsyncHttpApiProvider
token now (after S): org.jclouds.rest.config.SyncToAsyncHttpApiProvider
{code}
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874989#comment-13874989
]
Andrew Phillips commented on JCLOUDS-427:
-
OK, this is interesting now...here's the error message:
ttrying to bind
'org.jclouds.rest.config.SyncToAsyncHttpApiProvider' to 'interface org.jclouds.rest.HttpClient'. Input async class: 'interface
org.jclouds.rest.HttpAsyncClient'
So somehow the {{.where(new TypeParameter() {}, async)}} part in
{code}
new TypeToken>() {
}.where(new TypeParameter() {
}, sync).where(new TypeParameter() {
}, async);
{code}
(https://github.com/jclouds/jclouds/blob/master/core/src/main/java/org/jclouds/rest/config/BinderUtils.java#L101)
is not getting A bound to HttpAsyncClient..?
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874879#comment-13874879
]
Andrew Phillips commented on JCLOUDS-427:
-
Added a branch to try to get some more debugging info on what exactly is going
on here:
https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=shortlog;h=refs/heads/JCLOUDS-427
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873762#comment-13873762
]
Andrew Phillips commented on JCLOUDS-427:
-
Hm...nothing in the release notes that would seem immediately related to this?
http://www.oracle.com/technetwork/java/javase/7u51-relnotes-2085002.html
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873743#comment-13873743
]
Andrew Phillips commented on JCLOUDS-427:
-
FYI: The jclouds Java 7 CI builds on DEV@cloud are running against 1.7.0_25:
Java version: 1.7.0_25, vendor: Oracle Corporation
Java home: /opt/java/sdk/Sun/x86_64/jdk1.7.0_25/jre
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873672#comment-13873672
]
graham o'regan commented on JCLOUDS-427:
Sure, I should have been clear, this isn't an issue with the test cases
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873665#comment-13873665
]
John Kew commented on JCLOUDS-427:
--
We discovered this yesterday in our staging environment after our jdk upgrade;
so it is not just a test regression.
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873637#comment-13873637
]
Andrew Bayer commented on JCLOUDS-427:
--
For confirmation, see
https://jclouds.ci.cloudbees.com/job/jclouds-java-7u51/1/console
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
>
>
> Key: JCLOUDS-427
> URL: https://issues.apache.org/jira/browse/JCLOUDS-427
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 1.7.0, 1.6.3
>Reporter: graham o'regan
>
> Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
> interface implementations
> Running 'mvn test' results in test failures similar to this;
> {code}
> Caused by: com.google.inject.CreationException: Guice creation errors:
> 1)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 2)
> org.jclouds.rest.config.SyncToAsyncHttpApiProvider A> cannot be used as a key; It is not fully specified.
> 3) org.jclouds.rest.RestContext
> cannot be used as a key; It is not fully specified.
> 4) No implementation for org.jclouds.rest.HttpClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> 5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
> at
> org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
> {code}
> I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
> same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
