[
https://issues.apache.org/jira/browse/JCLOUDS-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864302#comment-16864302
]
Ignasi Barrera commented on JCLOUDS-1166:
-----------------------------------------
I agree it is not ideal, but it fixes the immediate issue and it does not
prevent jclouds from upgrading (see that only the internal offending package is
renamed, the rest remains exactly the same.
The ideal solution would be to remove the need of that package, but it requires
more effort, and jclouds is a pure volunteer project.
* Are you stepping to fix it the right way?
* This has been open for a long time. Lots of affected users. No real work on
this from anyone. If someone is willing to spend the time to contribute a
better fix, I'd be more than happy to review and merge it. Otherwise I'd
suggest to move forward and nblock people.
As said, this is a purely volunteer project and we are happy to accept
contributions... When they come :)
> 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
> Assignee: Ignasi Barrera
> Priority: Major
> Labels: gson
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
