[
https://issues.apache.org/jira/browse/JCLOUDS-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457730#comment-15457730
]
ASF subversion and git services commented on JCLOUDS-1160:
----------------------------------------------------------
Commit 4c9276366383cff415bbb4ea6130396f370993ea in jclouds's branch
refs/heads/master from [~nacx]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=4c92763 ]
Upgrade to Gson 2.5 instead of Gson 2.7
Related issues: JCLOUDS-1166, JCLOUDS-1160, JCLOUDS-1169
This change reverts commit da4614e and upgrades from Gson 2.3.1 to 2.5,
which is the last version that exports the internal packages, used in
jclouds-core, in the OSGi bundle.
> 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
> Assignee: Andrew Gaul
> Fix For: 2.0.0
>
>
> 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)
