[
https://issues.apache.org/jira/browse/DERBY-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127469#comment-15127469
]
Rick Hillegas commented on DERBY-6856:
--------------------------------------
Dalibor Topic, from the Oracle Java team, says that we have been
cross-compiling for older JVMs using a suspect trick. Simply setting
source=olderVersion and target=olderVersion is not good enough. We need to do
one of the following:
https://blogs.oracle.com/darcy/entry/how_to_cross_compile_for
or
http://openjdk.java.net/jeps/247
For more context, see the following email thread:
http://apache-database.10148.n7.nabble.com/Early-Access-builds-of-JDK-8u76-b02-JDK-9-build-b100-amp-build-b99-for-JDK-9-with-Project-Jigsaw-aret-td145290.html
> 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
>
> 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)
