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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2017/05/07 14:53:04 UTC
[jira] [Updated] (DERBY-6932) Migrate finalization to the new
Cleaner-based pattern introduced by JDK 9 build 167
[ https://issues.apache.org/jira/browse/DERBY-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-6932:
---------------------------------
Attachment: ClientConnection.patch
Attaching Peter Levart's solution for ClientConnection, also found at http://cr.openjdk.java.net/~plevart/misc/Cleaner/derby/ClientConnection_finalize2cleaner.patch
> Migrate finalization to the new Cleaner-based pattern introduced by JDK 9 build 167
> -----------------------------------------------------------------------------------
>
> Key: DERBY-6932
> URL: https://issues.apache.org/jira/browse/DERBY-6932
> Project: Derby
> Issue Type: Improvement
> Components: JDBC, Network Client, Network Server
> Affects Versions: 10.14.0.0
> Reporter: Rick Hillegas
> Attachments: ClientConnection.patch
>
>
> As of build 167, JDK 9 deprecated the finalize() method. This produces deprecation warnings when compiling several Derby classes. See https://issues.apache.org/jira/browse/DERBY-6856?focusedCommentId=15990011&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15990011 . The recommended fix is a non-trivial mini-project, viz., to migrate to a new finalization pattern based on a newly added Java 9 class, java.lang.ref.Cleaner. Peter Levart kindly mocked up the fix for one affected Derby class (ClientConnection). See http://cr.openjdk.java.net/~plevart/misc/Cleaner/derby/ClientConnection_finalize2cleaner.patch
> Further discussion can be found on the following open-jdk email thread: http://mail.openjdk.java.net/pipermail/core-libs-dev/2017-May/047417.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)