[
https://issues.apache.org/jira/browse/DERBY-6518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161829#comment-14161829
]
Rick Hillegas commented on DERBY-6518:
--------------------------------------
Note that the sealing violation described by DERBY-6756 is ultimately caused by
the fact that JVMInfo is included in both the client and engine jar files.
There are several classes in the org.apache.derby.iapi.services.info package
besides JVMInfo. They all have the potential of causing sealing violations in
the future.
> 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,
> derby-6518-02-aa-cloneSplitMethod.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)
