You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Gaul (JIRA)" <ji...@apache.org> on 2015/08/04 20:12:04 UTC

[jira] [Resolved] (JCLOUDS-974) GSON 2.3 pom is buggy, use 2.3.1 instead

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

Andrew Gaul resolved JCLOUDS-974.
---------------------------------
       Resolution: Fixed
         Assignee: Andrew Gaul
    Fix Version/s: 2.0.0

If we can find a way to reproduce these symptoms we can backport to 1.9.x however there will not likely be further releases from this branch.

> GSON 2.3 pom is buggy, use 2.3.1 instead
> ----------------------------------------
>
>                 Key: JCLOUDS-974
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-974
>             Project: jclouds
>          Issue Type: Bug
>    Affects Versions: 1.9.0
>            Reporter: Paul Merlin
>            Assignee: Andrew Gaul
>             Fix For: 2.0.0
>
>
> Gson pom for 2.3 contains a small mistake that turns into some "syntax error" with some maven versions.
> It happened on builds.a.o: http://s.apache.org/lGu
> I can't tell the exact maven version that was on that slave.
> I found these Gson issues:
> - https://github.com/google/gson/issues/596
> - https://github.com/google/gson/issues/588
> - https://github.com/google/gson/commit/6580921f9d6f399a6bc20355d83aea60168d8d5c
> In these, users report Maven 2.x, 3.0.4, 3.2.2, 3.2.3 as exhibiting the issue.
> Reported as working: Maven 3.0.5, 3.1.1, 3.3.3.
> JClouds depends on Gson 2.3, see JCLOUDS-719.
> This is fixed in Gson 2.3.1.



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