[ https://issues.apache.org/jira/browse/DERBY-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296085#comment-15296085 ]
Knut Anders Hatlen commented on DERBY-6856: ------------------------------------------- Hi Rick, If you use getDeclaredConstructor() instead of getConstructor(), you might not have to make the constructors public. getConstructor() only finds public constructors, whereas getDeclaredConstructor() also finds non-public constructors. > 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-6856-04-aa-autoboxingDeprecationWarnings-part2.diff, > derby-6856-04-ab-autoboxingDeprecationWarnings-part2.diff, > derby-6856-05-ac-roundingMode-Class.newInstance.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)