[jira] [Commented] (PIVOT-993) Apache Pivot does not work with Oracle JDK8u131

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (PIVOT-993) Apache Pivot does not work with Oracle JDK8u131

JIRA jira@apache.org

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

Todd Volkert commented on PIVOT-993:
------------------------------------

I'm getting users of my app unable to run it due to this bug (since we try to parse the Java version in ApplicationContext's static initializer block).

In my case, I'm still on Pivot 1.4, so I'm just going to have to patch a local fix since updating to Pivot 2.0 is beyond the scope of my work.

> Apache Pivot does not work with Oracle JDK8u131
> -----------------------------------------------
>
>                 Key: PIVOT-993
>                 URL: https://issues.apache.org/jira/browse/PIVOT-993
>             Project: Pivot
>          Issue Type: Bug
>          Components: all
>    Affects Versions: 2.0.4
>         Environment: java version "1.8.0_131"
> Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
> Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
>            Reporter: Andres Almiray
>            Assignee: Sandro Martini
>            Priority: Critical
>             Fix For: 2.1, 2.0.5
>
>
> Attempting to run a Pivot application with Oracle JDK8u131 results in the following stacktrace
> {code}
> Caused by: java.lang.NumberFormatException: Value out of range. Value:"131" Radix:10
> at java.lang.Byte.parseByte(Byte.java:151)
> at java.lang.Byte.parseByte(Byte.java:175)
> at org.apache.pivot.util.Version.decode(Version.java:150)
> at org.apache.pivot.wtk.ApplicationContext.<clinit>(ApplicationContext.java:1697)
> ... 15 more
> {code}
> The problem is located in the `Version` class. This class parses version numbers using Byte. 131 is clearly out of range. Should use `Short` or `Integer` instead.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)