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/06/15 17:12:00 UTC

[jira] [Commented] (DERBY-7110) Make it possible to build and test Derby cleanly with OpenJDK 17

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

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

When I tried to build Derby with the Rampdown Phase One build of open JDK 17 (17-ea+26-2439), I saw many warnings related to the deprecation of Security Manager classes and methods, undoubtedly the consequence of JEP 411 (https://openjdk.java.net/jeps/411). Derby, like Tomcat, embraced the Security Manager early on. Permissions checks were rototilled across the whole code base and our distributions ship with several template policy files, which we encourage users to customize for their environments. The "Configuring Java Security" section of our Security Guide explains how to do this (https://db.apache.org/derby/docs/10.15/security/index.html).

My build only reported the first 100 warnings. It is likely that there are many more. The warnings look like this:

{noformat}
    [javac] /Users/rhillegas/derby/mainline/trunk/java/org.apache.derby.client/org/apache/derby/client/BasicClientDataSource.java:675: warning: [removal] AccessController in java.security has been deprecated and marked for removal
    [javac]         return AccessController.doPrivileged(new PrivilegedAction<String>() {
{noformat}

On the advice of Rory O'Donnell (see http://apache-database.10148.n7.nabble.com/JDK-17-is-now-in-Rampdown-Phase-One-td151971.html), I took this issue to the security-dev@openjdk.java.net mailing list. There, Alan Bateman from the Java security team recommended that I decorate these 100s of instances with @SuppressWarnings("removal") annotations--until the Java security team comes up with a replacement for the security manager.

I will try out this solution.


> Make it possible to build and test Derby cleanly with OpenJDK 17
> ----------------------------------------------------------------
>
>                 Key: DERBY-7110
>                 URL: https://issues.apache.org/jira/browse/DERBY-7110
>             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-7110-01-aa-removeAngleBrackets.diff
>
>
> Releases of Open JDK 17 can be found at https://jdk.java.net/17/. 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)