db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-6518) JVMInfo should not use parseFloat() to parse java.specification.version
Date Wed, 26 Mar 2014 10:10:17 GMT

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

Knut Anders Hatlen resolved DERBY-6518.
---------------------------------------

          Resolution: Fixed
       Fix Version/s: 10.11.0.0
    Issue & fix info:   (was: Patch Available)

> 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: Knut Anders Hatlen
>             Fix For: 10.11.0.0
>
>         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.2#6252)

Mime
View raw message