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

Rick Hillegas updated DERBY-6854:
---------------------------------
    Attachment: derby-6854-01-aa-fixFor9-ea.diff

Attaching derby-6854-01-aa-fixFor9-ea.diff. This patch makes JavaVersionHolder 
recognize the version strings used by build 100 of Java 9. This patch also 
disables the UnsupportedVetter test on Java 9. That test fails there for 
reasons explained by DERBY-6855. The tests now run cleanly for me when I build 
Derby with Java 8 and run the tests on Java 9. I will re-run the tests on Java 
8 to make sure that these changes haven't destabilized the regression tests on 
that platform.

Note that you can't build Derby on Java 9 now, for reasons explained by 
DERBY-6856. This means that we can't verify the interesting combination of a 
Derby built and tested on Java 9.


Touches the following files:

M       
java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/UnsupportedVetter.java
M       
java/testing/org/apache/derbyTesting/functionTests/harness/JavaVersionHolder.java


> 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)

Reply via email to