[
https://issues.apache.org/jira/browse/DERBY-6518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6518:
---------------------------------
Attachment: derby-6518-01-aa-use-StringUtil.diff
Attaching derby-6518-01-aa-use-StringUtil.diff. This patch changes JVMInfo to
use StringUtil.split() instead. With this fix the Derby build succeeds on my
machine. There was no regression test case for the original problem, so I can
only hope that this works correctly.
Touches the following file:
M java/engine/org/apache/derby/iapi/services/info/JVMInfo.java
> 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, derby-6518-01-aa-use-StringUtil.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)
