db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6854) Make it possible to run Derby tests on early access versions of JDK 9
Date Wed, 27 Apr 2016 20:03:13 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260838#comment-15260838
] 

ASF subversion and git services commented on DERBY-6854:
--------------------------------------------------------

Commit 1741324 from [~knutanders] in branch 'code/branches/10.11'
[ https://svn.apache.org/r1741324 ]

DERBY-6854: Make it possible to run Derby tests on early access versions of JDK 9
DERBY-6881: Test failures with JDK 9-ea b111

Merged revision 1741311 from the 10.12 branch.

> 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
>         Attachments: derby-6854-01-aa-fixFor9-ea.diff
>
>
> Early access versions of JDK 9 (build 100) have "9-ea" as the java.version and "9" as
the java.specification.version. This confuses 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)

Mime
View raw message