[
https://issues.apache.org/jira/browse/DERBY-7126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17446515#comment-17446515
]
Bryan Pendleton commented on DERBY-7126:
----------------------------------------
It's starting to feel a bit as though JDK 18 will be a watershed release for
Derby with some external consequences similar in scope to JDK 9, though
internally of course the situation with the two Java releases is very different.
I'm wondering if we should lay the groundwork to have a new major release of
Derby, just as we did with JDK 9, so we'd have:
* People who are still using JDK 8 (yes, amazingly, still a large user base):
stick with Derby 10.14
* People who have moved to JDK 9-JDK 17: use Derby 10.15
* People who have moved to JDK 18+: use Derby 10.16
> Make it possible to build and test Derby cleanly with OpenJDK 18
> ----------------------------------------------------------------
>
> Key: DERBY-7126
> URL: https://issues.apache.org/jira/browse/DERBY-7126
> 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_7126_A.java, DERBY_7126_B.java, dcl_emc2sm.jar,
> derby-7126-01-aa-regenerateSignedJars.diff,
> derby-7126-02-aa-suppressDeprecationWarnings.diff
>
>
> Releases of Open JDK 18 can be found at https://jdk.java.net/178. We should
> adjust Derby as necessary so that it builds cleanly (including javadoc) and
> tests cleanly with this version of the platform.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
