[ https://issues.apache.org/jira/browse/DERBY-7126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435005#comment-17435005 ]
Bryan Pendleton commented on DERBY-7126: ---------------------------------------- This is interesting, thanks for posting the details! I assume that JDK 18 is dropping support for SHA1 because they are trying to force everyone to move to something newer and stronger (is there a SHA2?). Assuming there is a newer replacement, probably we need to figure out how to test with that newer replacement I guess? But it also seems like if JDK doesn't support a certain signing level (that is, SHA1), then it should raise an error, not just quietly disregard the signature. > 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 > > > 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.3.4#803005)