[
https://issues.apache.org/jira/browse/DERBY-7126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510686#comment-17510686
]
Richard N. Hillegas commented on DERBY-7126:
--------------------------------------------
Hi Brian. I think that's a good idea. Here's what I think the next steps are:
1) I can verify today that Derby builds cleanly with JDK 17 and tests cleanly
when -Djava.security.manager=allow is set.
2) Write a release note explaining the deprecation of the SecurityManager. The
note should say that when you run the network server on JDK 17 or higher, then
you need to set either -Djava.security.manager=allow or -noSecurityManager.
3) Discuss with the community the need to compile 10.16 into JDK 17 byte code
so that it won't run on earlier releases. I think that's the way to avoid the
problems associated with the changed meaning of -Djava.security.manager.
4) Compile a 10.16 release with JDK 17, vet it, and publish it.
Going forward, I don't want to claim support for non LTS Java versions. The
association would be
10.14 runs on Java 8.
10.15 runs on Java 11.
10.16 runs on Java 17.
What are your thoughts?
> 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,
> derby-7126-03-aa-mention-java.security.manager.diff,
> derby-7126-04-aa-makeTestsRunOnJDK11andJDK18.diff,
> derby-7126-05-aa-suppressRemovalWarnings.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)
