[
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-ad-base.diff
Attaching derby-6856-XX-ad-base.diff. This patch is the new set of changes
required to compile and test Derby with builds of jdk 9. This patch reflects
the migration of the Taglet classes from jdk.javadoc.doclet.taglet to
jdk.javadoc.doclet. With this patch, Derby compiles cleanly under jdk 9 b162.
However, when I try to build the javadoc, I see the following errors:
{noformat}
[javadoc] javadoc: error - An internal exception has occurred.
[javadoc] (java.lang.NullPointerException)
[javadoc] Please file a bug against the javadoc tool via the Java bug
reporting page
[javadoc] (http://bugreport.java.com) after checking the Bug Database
(http://bugs.java.com)
[javadoc] for duplicates. Include error messages and the following diagnostic
in your report. Thank you.
[javadoc] java.lang.NullPointerException
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.JavaScriptScanner.visitAttribute(JavaScriptScanner.java:98)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.JavaScriptScanner.visitAttribute(JavaScriptScanner.java:46)
[javadoc] at
jdk.compiler/com.sun.tools.javac.tree.DCTree$DCAttribute.accept(DCTree.java:190)
[javadoc] at
jdk.compiler/com.sun.source.util.DocTreePathScanner.scan(DocTreePathScanner.java:71)
[javadoc] at
jdk.compiler/com.sun.source.util.DocTreeScanner.scan(DocTreeScanner.java:98)
[javadoc] at
jdk.compiler/com.sun.source.util.DocTreeScanner.visitStartElement(DocTreeScanner.java:437)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.JavaScriptScanner.visitStartElement(JavaScriptScanner.java:57)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.JavaScriptScanner.visitStartElement(JavaScriptScanner.java:46)
[javadoc] at
jdk.compiler/com.sun.tools.javac.tree.DCTree$DCStartElement.accept(DCTree.java:810)
[javadoc] at
jdk.compiler/com.sun.source.util.DocTreePathScanner.scan(DocTreePathScanner.java:71)
[javadoc] at
jdk.compiler/com.sun.source.util.DocTreeScanner.scanAndReduce(DocTreeScanner.java:83)
[javadoc] at
jdk.compiler/com.sun.source.util.DocTreeScanner.scan(DocTreeScanner.java:98)
[javadoc] at
jdk.compiler/com.sun.source.util.DocTreeScanner.scanAndReduce(DocTreeScanner.java:106)
[javadoc] at
jdk.compiler/com.sun.source.util.DocTreeScanner.visitDocComment(DocTreeScanner.java:184)
[javadoc] at
jdk.compiler/com.sun.tools.javac.tree.DCTree$DCDocComment.accept(DCTree.java:132)
[javadoc] at
jdk.compiler/com.sun.source.util.DocTreePathScanner.scan(DocTreePathScanner.java:50)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.JavaScriptScanner.scan(JavaScriptScanner.java:49)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.Utils.getDocCommentTree0(Utils.java:3037)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.Utils.getDocCommentTree(Utils.java:3088)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.Utils$WeakSoftHashMap.computeIfAbsent(Utils.java:3270)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.Utils.getCommentHelper(Utils.java:2878)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.Utils.hasBlockTag(Utils.java:2960)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.Utils.hasBlockTag(Utils.java:2956)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.Utils.isHidden(Utils.java:1556)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.ClassTree.buildTree(ClassTree.java:177)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.ClassTree.<init>(ClassTree.java:120)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:205)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.AbstractDoclet.run(AbstractDoclet.java:117)
[javadoc] at
jdk.javadoc/jdk.javadoc.doclet.StandardDoclet.run(StandardDoclet.java:68)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.tool.Start.parseAndExecute(Start.java:608)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.tool.Start.begin(Start.java:424)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.tool.Start.begin(Start.java:341)
[javadoc] at
jdk.javadoc/jdk.javadoc.internal.tool.Main.execute(Main.java:63)
[javadoc] at jdk.javadoc/jdk.javadoc.internal.tool.Main.main(Main.java:52)
{noformat}
> 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, 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)
