You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Jia Zhai (JIRA)" <ji...@apache.org> on 2019/03/27 08:41:00 UTC
[jira] [Commented] (JCLOUDS-1166) Remove uses of the
'com.google.gson.internal' package
[ https://issues.apache.org/jira/browse/JCLOUDS-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802552#comment-16802552 ]
Jia Zhai commented on JCLOUDS-1166:
-----------------------------------
[~nacx] Thanks for the help on this issue.
Is there any plan to fix this gson conflict issue?
> Remove uses of the 'com.google.gson.internal' package
> -----------------------------------------------------
>
> Key: JCLOUDS-1166
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1166
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-chef, jclouds-core
> Affects Versions: 1.9.2
> Reporter: Ignasi Barrera
> Priority: Major
> Labels: gson
>
> Starting from Gson 2.6, the {{com.google.gson.internal}} packages are no longer exported in the OSGi bundles. This makes it impossible to use jclouds in an OSGi environment if upgrading to such versions of Gson.
> There is no change to add the exports back for that package (see [this discussion|https://github.com/google/gson/pull/916]), so we should stop using those classes.
> See also: http://markmail.org/message/olgebygfgdy3hwtm
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)