[ 
https://issues.apache.org/jira/browse/JCLOUDS-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17585639#comment-17585639
 ] 

Andrew Gaul commented on JCLOUDS-1618:
--------------------------------------

This is due to an API change from gson 2.8.9 to 2.9.0.  I tried to patch up 
jclouds but encountered an issue with bnd.  It would be great if you could 
investigate this further.  You can check out my WIP branch here:

https://github.com/gaul/jclouds-1/pull/new/deps/gson-291

> Jclouds 2.3.0 and above is incompatible with SpringBoot 2.7.*
> -------------------------------------------------------------
>
>                 Key: JCLOUDS-1618
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1618
>             Project: jclouds
>          Issue Type: Bug
>    Affects Versions: 2.3.0, 2.4.0, 2.5.0
>            Reporter: Biswa Ranjan Ray
>            Assignee: Andrew Gaul
>            Priority: Major
>         Attachments: JClouds_Gson_Error.txt
>
>
> Hi,
> We developed a multi-cloud application using jclouds and springboot to 
> support operations on storage services e.g s3, gcs and azure storage.
> We're trying to migrate our application from springboot 2.5.* to latest 
> (springboot 2.7.*). However we're facing issues with jclouds. Its observed 
> that errors are thrown during the creation of BlobStoreContext. A full 
> stacktrace is attached.
> Here is a code snippet of BlobStoreContext:
> public BlobStoreContext getBlobStoreContext()
> {    
>    return ContextBuilder.newBuilder(CloudProviders.PROVIDER_AWS.toString())   
>           
>    .credentials(this.getAccessKeyId(), this.getSecretAccessKey())             
>    .buildView(BlobStoreContext.class);
> }
> We also tried jclouds 2.4.0 & 2.5.0 but no luck. However its found jclouds 
> 2.3.0 is compatible with springboot 2.6.10 and currently we're using the 
> same, but our goal is to upgrade to springboot 2.7.   
> Any suggestions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to