[
https://issues.apache.org/jira/browse/JCLOUDS-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856366#comment-16856366
]
Olaf Flebbe commented on JCLOUDS-1166:
--------------------------------------
[~nacx] I do not quite understand why jclouds should go to the copy approach.
It is a maintenance nightmare, nobody seems wanting to implement, the
dependency is put into a different project so the real need for continuation
has been sidestepped. If we are going to copy the source into jclouds we would
never had to move jclouds-cli out. I understood this move as a way to solve
this problem by simply ignoring.
My vote is to break OSGI intentionally.
> 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)
