You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Ignasi Barrera (JIRA)" <ji...@apache.org> on 2016/08/27 22:12:20 UTC

[jira] [Commented] (JCLOUDS-1160) Consider gson 2.7 upgrade

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

Ignasi Barrera commented on JCLOUDS-1160:
-----------------------------------------

Looking at the release notes I don't see any breaking changes.

It also includes an improvement to the {{@SeriualizedName}} annotation that makes it work with AutoValue. That would make it possible to eliminate the current need to have the fields declared in the same order than they are passed as parameters to the factory methods. 

+1 to add is ASAP and make this part of 2.0. [~andrewp] WDYT?

> Consider gson 2.7 upgrade
> -------------------------
>
>                 Key: JCLOUDS-1160
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1160
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-core
>    Affects Versions: 1.9.0
>            Reporter: Andrew Gaul
>
> An S3Proxy user complained about not being able to include it in his application with a Spring Boot 1.4 dependency due to gson conflicts:
> https://github.com/andrewgaul/s3proxy/issues/148
> https://github.com/spring-projects/spring-boot/issues/6761
> We should consider upgrading to gson 2.7 in master.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)