[jira] [Commented] (JCLOUDS-1074) Compatibility with Guava 20
[ https://issues.apache.org/jira/browse/JCLOUDS-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469541#comment-15469541 ] ASF subversion and git services commented on JCLOUDS-1074: -- Commit 7cde28a4d2af3cde0adec62186b19116893b06f2 in jclouds's branch refs/heads/master from [~gaul] [ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=7cde28a ] JCLOUDS-1074: Guava 20 compatibility * dynamically call TypeToken.isSupertypeOf with Guava 19 and later and TypeToken.isAssignableFrom with Guava 18 and earlier * consume or ignore values from methods with CheckReturnValue * replace usage of removed Iterators.emptyIterator > Compatibility with Guava 20 > --- > > Key: JCLOUDS-1074 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1074 > Project: jclouds > Issue Type: Bug > Components: jclouds-core >Affects Versions: 2.0.0 >Reporter: Olivier Voortman > Labels: guava > > Hello, > It seems jclouds is still using some deprecated methods from the Guava > library, which are now removed from version 20.0-SNAPSHOT. > For example : > java.lang.NoSuchMethodError: > com.google.common.reflect.TypeToken.isAssignableFrom(Lcom/google/common/reflect/TypeToken;)Z > Used here : > org.jclouds.apis.Apis$1.apply(Apis.java:134) > See removal of those methods from Guava here : > https://github.com/google/guava/commit/f001be54c2e3676d39623942e96b97699d42467a > This should be quite easy to fix. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JCLOUDS-1074) Compatibility with Guava 20
[ https://issues.apache.org/jira/browse/JCLOUDS-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346446#comment-15346446 ] Olivier Voortman commented on JCLOUDS-1074: --- I think sticking with an outdated version of guava is not a good idea. People will want to upgrade to the latest guava version. I personally don't care, but some of my dependencies require a more recent version. If it's not possible, maybe you could repackage the correct version inside your own jar files? > Compatibility with Guava 20 > --- > > Key: JCLOUDS-1074 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1074 > Project: jclouds > Issue Type: Bug > Components: jclouds-core >Affects Versions: 2.0.0 >Reporter: Olivier Voortman > Labels: guava > > Hello, > It seems jclouds is still using some deprecated methods from the Guava > library, which are now removed from version 20.0-SNAPSHOT. > For example : > java.lang.NoSuchMethodError: > com.google.common.reflect.TypeToken.isAssignableFrom(Lcom/google/common/reflect/TypeToken;)Z > Used here : > org.jclouds.apis.Apis$1.apply(Apis.java:134) > See removal of those methods from Guava here : > https://github.com/google/guava/commit/f001be54c2e3676d39623942e96b97699d42467a > This should be quite easy to fix. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JCLOUDS-1074) Compatibility with Guava 20
[
https://issues.apache.org/jira/browse/JCLOUDS-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15133132#comment-15133132
]
Andrew Gaul commented on JCLOUDS-1074:
--
Unfortunately the replacement, {{TypeToken.isSupertypeOf}}, was introduced in
Guava 19. jclouds currently supports Guava 16.0.1 and previous upgrades have
proven contentious.
> Compatibility with Guava 20
> ---
>
> Key: JCLOUDS-1074
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1074
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
>Affects Versions: 2.0.0
>Reporter: Olivier Voortman
> Labels: guava
>
> Hello,
> It seems jclouds is still using some deprecated methods from the Guava
> library, which are now removed from version 20.0-SNAPSHOT.
> For example :
> java.lang.NoSuchMethodError:
> com.google.common.reflect.TypeToken.isAssignableFrom(Lcom/google/common/reflect/TypeToken;)Z
> Used here :
> org.jclouds.apis.Apis$1.apply(Apis.java:134)
> See removal of those methods from Guava here :
> https://github.com/google/guava/commit/f001be54c2e3676d39623942e96b97699d42467a
> This should be quite easy to fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
