[
https://issues.apache.org/jira/browse/JCLOUDS-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16860068#comment-16860068
]
Ignasi Barrera commented on JCLOUDS-1166:
-----------------------------------------
The move of karaf and cli to the Karaf community was not because of this issue.
Was for the inability for us to keep in sync with Karaf releases and being
unable to properly upgrade to newer ones.
I will implement this and copy the files. It is not a big deal. I mean, being
unable to upgrade the library and copying the bits you need it is pretty much
the same. Maintenance nightmare is not gonna be there as we need just a few
utility methods for reflection and some other small nits.
I plan to do this as soon as I can, but unfortunately I haven't had time to do
it yet.
There is no need to break OSGi and I think, given the relatively simple way we
have to keep it working, it's not worth it.
> 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)
