[jira] [Commented] (JCLOUDS-1491) Jclouds uses a deprecated version of Guava to support Azure storage.
[
https://issues.apache.org/jira/browse/JCLOUDS-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150456#comment-17150456
]
Biswa Ranjan Ray commented on JCLOUDS-1491:
---
We have upgraded our application to use jclouds 2.2.0 and still using guava
27.0.1-jre. Is the above fix available in jclouds 2.2.0 ? If not can you please
suggest us which version of guava can be used with jclouds 2.2.0.
Thank you.
> Jclouds uses a deprecated version of Guava to support Azure storage.
>
>
> Key: JCLOUDS-1491
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1491
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
>Affects Versions: 2.2.1
>Reporter: Biswa Ranjan Ray
>Assignee: Andrew Gaul
>Priority: Major
> Labels: azureblob
> Fix For: 2.3.0
>
> Attachments: jclouds_issue.txt
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Hi,
> We are facing an issue while using jclouds library along with Guava to
> support Azure storage.
> *Issue:*
> We are using Jclouds 2.1.2 and Guava 27.0.1-jre in our application to work
> with objectstore service offered by several cloud providers. These libraries
> works seamlessly for AWS S3 and GCS. But in case of azure we get an
> exception. Please see the attachment for stack trace.
> *Analysis:*
> We found that the issue is there with the below code in DnsValidator class at
> line 53:
> {code:java}
> if (CharMatcher.JAVA_LETTER_OR_DIGIT.indexIn(name) != 0)
> {code}
> The above static field is deprecated in Guava 27.0.1-jre. But apparently
> jclouds library still refers to a deprecated version of Guava as mentioned in
> the jclouds doc:
> {quote}Setup your project to include 'guava'. Include following dependency to
> jclouds Installation. Update the version mentioned in dependency below to the
> latest available version. com.google.guava guava 16.0
> {quote}
> If not the latest at least we would like to use the recent version of Guava.
> But Guava 16.0 is really old and deprecated as well. Any thoughts are
> appreciated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JCLOUDS-1491) Jclouds uses a deprecated version of Guava to support Azure storage.
[
https://issues.apache.org/jira/browse/JCLOUDS-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17124471#comment-17124471
]
ASF subversion and git services commented on JCLOUDS-1491:
--
Commit 20b1394f36dd9e522f2173b344f85a04988ae720 in jclouds's branch
refs/heads/master from Jean-Noël Rouvignac
[ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=20b1394 ]
JCLOUDS-1491 Jclouds uses a deprecated version of Guava to support Azure storage
DnsNameValidator.java uses a deprecated guava APIs in code that is used
to support Azure cloud storage. When forcing the use of more recent guava
versions, the code fails with NoSuchFieldError.
However, CharMatcher.JAVA_LETTER_OR_DIGIT has been removed in guava 26.0,
and CharMatcher.javaLetterOrDigit() should be used instead since guava
19.0. Note that CharMatcher.javaLetterOrDigit() was immediately
deprecated in Guava 26.0, and java.lang.Character.isLetterOrDigit(int)
should be used instead.
This commit replaces the use of this deprecated API by
java.lang.Character.isLetterOrDigit(int).
It is no worse than the previous code.
(If I understand correctly, updating the guava version is a challenge due to
dependencies on Apache Karaf anyway)
> Jclouds uses a deprecated version of Guava to support Azure storage.
>
>
> Key: JCLOUDS-1491
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1491
> Project: jclouds
> Issue Type: Improvement
>Reporter: Biswa Ranjan Ray
>Assignee: Daniel Estevez
>Priority: Major
> Attachments: jclouds_issue.txt
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Hi,
> We are facing an issue while using jclouds library along with Guava to
> support Azure storage.
> *Issue:*
> We are using Jclouds 2.1.2 and Guava 27.0.1-jre in our application to work
> with objectstore service offered by several cloud providers. These libraries
> works seamlessly for AWS S3 and GCS. But in case of azure we get an
> exception. Please see the attachment for stack trace.
> *Analysis:*
> We found that the issue is there with the below code in DnsValidator class at
> line 53:
> {code:java}
> if (CharMatcher.JAVA_LETTER_OR_DIGIT.indexIn(name) != 0)
> {code}
> The above static field is deprecated in Guava 27.0.1-jre. But apparently
> jclouds library still refers to a deprecated version of Guava as mentioned in
> the jclouds doc:
> {quote}Setup your project to include 'guava'. Include following dependency to
> jclouds Installation. Update the version mentioned in dependency below to the
> latest available version. com.google.guava guava 16.0
> {quote}
> If not the latest at least we would like to use the recent version of Guava.
> But Guava 16.0 is really old and deprecated as well. Any thoughts are
> appreciated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JCLOUDS-1491) Jclouds uses a deprecated version of Guava to support Azure storage.
[
https://issues.apache.org/jira/browse/JCLOUDS-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795716#comment-16795716
]
Biswa Ranjan Ray commented on JCLOUDS-1491:
---
[~gaul] Thanks for the update.
> Jclouds uses a deprecated version of Guava to support Azure storage.
>
>
> Key: JCLOUDS-1491
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1491
> Project: jclouds
> Issue Type: Improvement
>Reporter: Biswa Ranjan Ray
>Priority: Major
> Attachments: jclouds_issue.txt
>
>
> Hi,
> We are facing an issue while using jclouds library along with Guava to
> support Azure storage.
> *Issue:*
> We are using Jclouds 2.1.2 and Guava 27.0.1-jre in our application to work
> with objectstore service offered by several cloud providers. These libraries
> works seamlessly for AWS S3 and GCS. But in case of azure we get an
> exception. Please see the attachment for stack trace.
> *Analysis:*
> We found that the issue is there with the below code in DnsValidator class at
> line 53:
> {code:java}
> if (CharMatcher.JAVA_LETTER_OR_DIGIT.indexIn(name) != 0)
> {code}
> The above static field is deprecated in Guava 27.0.1-jre. But apparently
> jclouds library still refers to a deprecated version of Guava as mentioned in
> the jclouds doc:
> {quote}Setup your project to include 'guava'. Include following dependency to
> jclouds Installation. Update the version mentioned in dependency below to the
> latest available version. com.google.guava guava 16.0
> {quote}
> If not the latest at least we would like to use the recent version of Guava.
> But Guava 16.0 is really old and deprecated as well. Any thoughts are
> appreciated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JCLOUDS-1491) Jclouds uses a deprecated version of Guava to support Azure storage.
[
https://issues.apache.org/jira/browse/JCLOUDS-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16792499#comment-16792499
]
Andrew Gaul commented on JCLOUDS-1491:
--
We hope to upgrade Guava to 21 when moving to Java 8. Unfortunately this is
blocked on Karaf for now.
> Jclouds uses a deprecated version of Guava to support Azure storage.
>
>
> Key: JCLOUDS-1491
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1491
> Project: jclouds
> Issue Type: Improvement
>Reporter: Biswa Ranjan Ray
>Priority: Major
> Attachments: jclouds_issue.txt
>
>
> Hi,
> We are facing an issue while using jclouds library along with Guava to
> support Azure storage.
> *Issue:*
> We are using Jclouds 2.1.2 and Guava 27.0.1-jre in our application to work
> with objectstore service offered by several cloud providers. These libraries
> works seamlessly for AWS S3 and GCS. But in case of azure we get an
> exception. Please see the attachment for stack trace.
> *Analysis:*
> We found that the issue is there with the below code in DnsValidator class at
> line 53:
> {code:java}
> if (CharMatcher.JAVA_LETTER_OR_DIGIT.indexIn(name) != 0)
> {code}
> The above code is deprecated in Guava 27.0.1-jre. But apparently jclouds
> library still refers to a deprecated version of Guava as mentioned in the
> jclouds doc:
> {quote}Setup your project to include 'guava'. Include following dependency to
> jclouds Installation. Update the version mentioned in dependency below to the
> latest available version. com.google.guava guava 16.0
> {quote}
> If not the latest at least we would like to use the recent version of Guava.
> But Guava 16.0 is really old and deprecated as well. Any thoughts are
> appreciated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
