[
https://issues.apache.org/jira/browse/DERBY-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747555#comment-16747555
]
Rick Hillegas commented on DERBY-7028:
--------------------------------------
Hey Bryan,
Sorry for the confusion.
If you build the public javadoc with JDK 9 or 10, then there will be one copy
of each of the module diagrams. All of them will be located in the top level
directory of the javadoc, next to index.html. Coincidentally, that is the same
directory where the module overview pages are written.
If you build the public javadoc with JDK 11, then there will also be one copy
of each of the module diagrams. But each of them will be in a separate
subdirectory. The engine diagram will be in the org.apache.derby.engine
subdirectory of the javadoc output, next to the overview page for that module.
And similarly for the other modules.
There will be only one release. It will be compiled by Open JDK 11 with source
and target levels both set to level 9 so that Java 9 byte code is produced. The
public api javadoc will have the directory structure created by JDK 11's
javadoc tool.
That structure differs from the structure of our Jenkins-built javadoc for the
trunk. The Jenkins build uses JDK 9.
Does that make sense? Thanks.
> Module diagrams missing from javadoc for 15.1.0.0 release candidate
> -------------------------------------------------------------------
>
> Key: DERBY-7028
> URL: https://issues.apache.org/jira/browse/DERBY-7028
> Project: Derby
> Issue Type: Bug
> Components: Build tools
> Affects Versions: 10.15.1.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Priority: Major
> Attachments: derby-7028-01-aa-jdkSpecificImageLocations.diff
>
>
> This must be fixed for the release.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
