db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6518) JVMInfo should not use parseFloat() to parse java.specification.version
Date Fri, 03 Oct 2014 17:01:34 GMT

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

Rick Hillegas commented on DERBY-6518:
--------------------------------------

Heads-up: The 1629234 backport breaks the build of 10.10 on my machine. That is because the
new version of JVMInfo calls java.lang.String.split(). That method does not appear in CDC/FP
1.1. Releases in the 10.10 family are supposed to run on that platform. Thanks.

> JVMInfo should not use parseFloat() to parse java.specification.version
> -----------------------------------------------------------------------
>
>                 Key: DERBY-6518
>                 URL: https://issues.apache.org/jira/browse/DERBY-6518
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>    Affects Versions: 10.10.1.1
>            Reporter: Knut Anders Hatlen
>            Assignee: Mike Matrigali
>             Fix For: 10.11.1.1
>
>         Attachments: d6518-1a.diff
>
>
> JVMInfo uses parseFloat() to parse the java.specification.version property. That won't
work correctly if the minor version has more than one digit. It should order the versions
like this:
> 1.7 < 1.8 < 1.9 < 1.10 < 1.11
> With parseFloat(), they are ordered like this instead:
> 1.10 < 1.11 < 1.7 < 1.8 < 1.9
> The result is that newer Java versions will be classified as older, less capable ones,
and some functionality might be disabled because Derby thinks the platform is not capable
of providing it.



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

Mime
View raw message