db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6856) Make it possible to build Derby using JDK 9
Date Sat, 07 May 2016 21:21:12 GMT

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

ASF subversion and git services commented on DERBY-6856:
--------------------------------------------------------

Commit 1742756 from [~bryanpendleton] in branch 'code/trunk'
[ https://svn.apache.org/r1742756 ]

DERBY-6856: Make it possible to build Derby using JDK 9

This change reverts one particular change from revision 1742289.

The java.util.List class supports two remove methods:
remove(Object o) and remove(int i). In the DatabaseMetaDataTest's
testGetTypeInfo test, there is a List<Integer>, and changing
the autoboxing code to call remove(Types.BOOLEAN) rather than
remove(new Integer(Types.BOOLEAN)) caused the JDK 8 compiler to
choose remove(int i) rather than remove(Object o), thus
causing failures in the upgrade test suite.

This change returns the test code to using the explicit
object creation in order to ensure we call remove(Object o).

> Make it possible to build Derby using JDK 9
> -------------------------------------------
>
>                 Key: DERBY-6856
>                 URL: https://issues.apache.org/jira/browse/DERBY-6856
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.12.1.1
>            Reporter: Rick Hillegas
>         Attachments: derby-6856-01-ab-addShardingKey.diff, derby-6856-01-ac-cleanup.diff,
derby-6856-02-aa-addShardingKey.diff, derby-6856-03-aa-autoboxingDeprecationWarnings.diff,
derby-6856-03-ab-autoboxingDeprecationWarnings.diff
>
>
> Derby can't be built with JDK 9. Java 9 introduces new JDBC classes like java.sql.ShardingKey
and methods which refer to these new classes.
> In addition, project Jigsaw has created a new way to name classes (see http://openjdk.java.net/jeps/220).
This breaks the PropertySetter build tool which we use so that old JVMs can compile Derby
and so that Derby can be compiled to run on old JVMs.
> It is likely that we will need to leave this issue open throughout the development cycle
of Java 9.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message