You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2014/03/18 11:10:42 UTC
[jira] [Created] (DERBY-6518) JVMInfo should not use parseFloat()
to parse java.specification.version
Knut Anders Hatlen created DERBY-6518:
-----------------------------------------
Summary: 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
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)