[jira] [Resolved] (OLINGO-901) Olingo 2.0.6 has hard requirement on gson 2.4

["Christian Amend (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OLINGO-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Amend resolved OLINGO-901.
------------------------------------
       Resolution: Fixed
         Assignee: Christian Amend
    Fix Version/s: V2 2.0.7

Thanks a lot for the contribution. I applied it with the following commit: https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=bef01c2881fff1e76c84c803fda041d4987dc8eb

> Olingo 2.0.6 has hard requirement on gson 2.4
> ---------------------------------------------
>
>                 Key: OLINGO-901
>                 URL: https://issues.apache.org/jira/browse/OLINGO-901
>             Project: Olingo
>          Issue Type: Bug
>    Affects Versions: V2 2.0.6
>            Reporter: Andrew Clemons
>            Assignee: Christian Amend
>             Fix For: V2 2.0.7
>
>         Attachments: 0001-OLINGO-901-Set-osgi-range-for-gson-to-include-2.2.patch
>
>
> gson was bumped to 2.4 before the olingo 2.0.6 release which caused the osgi metadata generated in the olingo bundles to set this as the min-version range.
> After this, it is impossible to only upgrade from olingo 2.0.5 to 2.0.6 in an osgi environment without also upgrading gson. If other components are also using gson, this can be problematic. It would be better if olingo did not bump this on a point release.
> See also mailing list:
> https://mail-archives.apache.org/mod_mbox/olingo-user/201603.mbox/browser



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)