[
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-XX-ab-base.diff
Attaching derby-6856-XX-ab-base.diff. This patch incorporates
derby-6856-02-aa-addShardingKey.diff and is the new base patch to apply every
time that we test out new early access builds of JDK 9. In addition to the
changes in derby-6856-02-aa-addShardingKey.diff, this patch re-works our
javadoc Taglets. We now see deprecation warnings when we compile those classes
with build 124 of JDK 9. I have re-written the Taglets to implement
jdk.javadoc.doclet.taglet.Taglet instead of the deprecated
com.sun.tools.doclets.Taglet. This involved re-working our Taglets to use a
Visitor pattern.
The Derby javadoc builds successfully with these changes. However, the Java 9
javadoc tool spews pages of warnings as it digests our javadoc. This is true
even without my changes to the Taglet implementations. I will tackle those
warnings next.
I will run the tests to verify that Derby behaves correctly when run on build
124 of JDK 9.
Touches the following files:
M java/build/org/apache/derbyBuild/javadoc/EndFormatTaglet.java
M java/build/org/apache/derbyBuild/javadoc/FormatIdTaglet.java
M java/build/org/apache/derbyBuild/javadoc/UpgradeTaglet.java
M java/build/org/apache/derbyBuild/javadoc/DiskLayoutTaglet.java
M java/build/org/apache/derbyBuild/javadoc/PurposeTaglet.java
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
> 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-XX-ab-base.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)
