[
https://issues.apache.org/jira/browse/JCLOUDS-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834504#comment-16834504
]
Ignasi Barrera commented on JCLOUDS-1166:
-----------------------------------------
The main issue here is that simply upgrading will break jclouds in OSGi, as the
classes we use in the {{internal}} packages won't be available there.
So, we have to make the call for the fix:
* 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?
* If we are going to the copy approach, then we should copy the relevant
classes and work towards refacotring the code so we don't need that stuff.
[~andrewp], [~gaul], [~jbonofre] thoughts?
> 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)
