[
https://issues.apache.org/jira/browse/DERBY-6518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158107#comment-14158107
]
ASF subversion and git services commented on DERBY-6518:
--------------------------------------------------------
Commit 1629234 from [email protected] in branch 'code/branches/10.10'
[ https://svn.apache.org/r1629234 ]
DERBY-6518: JVMInfo should not use parseFloat() to parse
java.specification.version
backported change #1581777 from trunk to 10.10 branch, some manual changes
were necessary as logic did not exactly apply to 10.10 vs 10.11 version.
Change the parse logic so that it recognizes that version 1.10 is greater than
1.9.
> 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)
