Quantcast

[jira] [Comment Edited] (DERBY-6856) Make it possible to build Derby using JDK 9

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Comment Edited] (DERBY-6856) Make it possible to build Derby using JDK 9

JIRA jira@apache.org

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

Kathey Marsden edited comment on DERBY-6856 at 4/12/17 5:18 PM:
----------------------------------------------------------------

I just wanted to say thank you Rick for this and past  work with the new JDK's.  Early testing and verification for Derby has been great for both  for Derby and for the JDK's being tested to pop bugs and compatibility issues early.   Also it keeps Derby running and relevant under the new JDK's.  Myrna has done a lot of this too work in the past too and both endeavors have  made a big difference in quality all around.

Thank you!


was (Author: kmarsden):
I just wanted to say thank you Rick for this and past  work with the new JDK's.  Early testing and verification for Derby has been great for both  for Derby and for the JDK's being tested to pop bugs and compatibility issues early.   Myrna has done a lot of this too work in the past too and both endeavors have  made a big difference in quality all around.

Thank you!

> 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-6856-05-af-roundingMode-Class.getDeclaredConstructor.diff, derby-6856-05-ag-roundingMode-Class.newInstance.diff, derby-6856-06-aa-observable.diff, derby-6856-07-aa-oneMoreNewInstance.diff, derby-6856-08-aa-cleanupJavadoc.diff, derby-6856-09-aa-javadocEntities.diff, derby-6856-10-aa-disable-permissions-subverting-test.diff, derby-6856-11-aa-jigsawResourceLocation.diff, derby-6856-XX-ab-base.diff, derby-6856-XX-ac-base.diff, derby-6856-XX-ad-base.diff, derby-6856-XX-ae-base.diff, PTest.java, ptestScript
>
>
> 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.15#6346)
Loading...