[
https://issues.apache.org/jira/browse/DERBY-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6856:
---------------------------------
Attachment: derby-6856-01-ab-addShardingKey.diff
Attaching derby-6856-01-ab-addShardingKey. This patch makes it possible to
build Derby using Java 9. Tests run cleanly on Java 9 with this patch. However,
this patch does not correctly cross-compile onto Java 8 for reasons described
in my previous comment. In any event, this approach would have likely failed
verification on some platforms. However, it is useful for verifying that Derby
runs correctly on evolving versions of Java 9.
Touches the following file:
----------------------------
D java/stubs/jdbc4
D java/stubs/jdbc4/java
Oddly, this cruft is still hanging around.
----------------------------
M java/demo/toursdb/build.xml
Fixed a warning when compiling with JDK9.
----------------------------
M java/engine/org/apache/derby/jdbc/EmbeddedXADataSourceInterface.java
M java/client/org/apache/derby/jdbc/ClientXADataSource.java
M java/client/org/apache/derby/jdbc/ClientXADataSourceInterface.java
M java/client/org/apache/derby/jdbc/ClientXADataSource40.java
M java/client/org/apache/derby/jdbc/BasicClientXADataSource40.java
Added unsupported method exceptions for new methods which return
ShardingKeyBuilder.
> 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 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)
