You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Eran Bergman (JIRA)" <ji...@apache.org> on 2019/08/14 16:32:00 UTC

[jira] [Commented] (JCLOUDS-1166) Remove uses of the 'com.google.gson.internal' package

    [ https://issues.apache.org/jira/browse/JCLOUDS-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16907411#comment-16907411 ] 

Eran Bergman commented on JCLOUDS-1166:
---------------------------------------

[~nacx] the work you have done on this is greatly appreciated but we can't make use of it if it isn't released.

What is the release process for JClouds and what should be done in order to start it? 
Is there a specific individual who is required to approve/perform such a release operation?

> 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: 1h 50m
>  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.14#76016)