Uploaded image for project: 'jclouds'
  1. jclouds
  2. JCLOUDS-1491

Jclouds uses a deprecated version of Guava to support Azure storage.

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.1
    • Fix Version/s: 2.3.0
    • Component/s: jclouds-core
    • Labels:

      Description

      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:

            if (CharMatcher.JAVA_LETTER_OR_DIGIT.indexIn(name) != 0)
      

      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:

      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

      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.

        Attachments

          Activity

            People

            • Assignee:
              gaul Andrew Gaul
              Reporter:
              roy.biswa Biswa Ranjan Ray

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 40m
                40m

                  Issue deployment