[
https://issues.apache.org/jira/browse/JCLOUDS-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16836091#comment-16836091
]
Andrew Phillips commented on JCLOUDS-1166:
------------------------------------------
> Now jclouds-karaf and jclouds-cli will be managed by the Apache Karaf
>community:
> If we go for the custom bundle approach (probably something that could land
> in ServiceMix), should the Karaf team take care of it?
> If not, where should we host/maintain that bundle?
Could we go for a approach along the lines of
[https://github.com/jclouds/jclouds-karaf/pull/77|https://github.com/jclouds/jclouds-karaf/pull/77/files]?
I.e. build a custom Gson 2.7 bundle as part of the jclouds-karaf build
process, as explored previously in this comment thread (#comment-16531179).
Would we need that bundle to be hosted anywhere for this to work?
> 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)
