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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2016/01/16 23:44:39 UTC

[jira] [Assigned] (DERBY-6854) Make it possible to run Derby tests on early access versions of JDK 9

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

Rick Hillegas reassigned DERBY-6854:
------------------------------------

    Assignee: Rick Hillegas

> Make it possible to run Derby tests on early access versions of JDK 9
> ---------------------------------------------------------------------
>
>                 Key: DERBY-6854
>                 URL: https://issues.apache.org/jira/browse/DERBY-6854
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.12.1.1
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>
> Early access versions of JDK 9 (build 100) have "9-ea" as the java.version and "9" as the java.specification.version. This confused the JavaVersionHolder class which the regression tests use in order to determine the vm level. At a minimum, we need to make JavaVersionHolder recognize these early access strings.
> This issue can be left open even after a fix is applied because we have no idea how java.version and java.specification.version are going to evolve over the remaining development cycle for JDK 9.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)