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 "Richard N. Hillegas (Jira)" <ji...@apache.org> on 2021/01/16 21:22:00 UTC

[jira] [Commented] (DERBY-7088) Make it possible to build and test Derby using JDK 16

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

Richard N. Hillegas commented on DERBY-7088:
--------------------------------------------

Derby and its javadoc build cleanly with JDK 16 early access build 32. Tests against those jars run cleanly with both the classpath and modulepath on both Java 11 and Java 16.

> Make it possible to build and test Derby using JDK 16
> -----------------------------------------------------
>
>                 Key: DERBY-7088
>                 URL: https://issues.apache.org/jira/browse/DERBY-7088
>             Project: Derby
>          Issue Type: Task
>          Components: Build tools
>    Affects Versions: 10.16.0.0
>            Reporter: Richard N. Hillegas
>            Assignee: Richard N. Hillegas
>            Priority: Major
>         Attachments: derby-7088-01-aa-runTestsOnJDK16EA.diff, derby-7088-02-aa-deprecatedThreadGroupMethods.diff
>
>
> Make sure that Derby builds and tests cleanly with JDK 16, starting with the early access versions. This issue should be kept open until JDK 16 goes GA.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)