[ https://issues.apache.org/jira/browse/JCLOUDS-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841920#comment-16841920 ]
Ignasi Barrera commented on JCLOUDS-1166: ----------------------------------------- Yes, we talked to the gson people: https://github.com/google/gson/pull/916 Ok, in the absence of more inputs I think we're going for the copying approach. That allows us to progressively move away from the conflicting code while keeping OSGi support. I don't see enough justification in dropping OSGi support just to have a quick fix when we have simple workarounds too. > 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)