[
https://issues.apache.org/jira/browse/JENA-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14015253#comment-14015253
]
Rob Vesse commented on JENA-683:
--------------------------------
I would suggest leaving the layout as is since people may want to build
individual modules and have individual module javadocs. The easiest thing to
do is to use the {{<link>}} configuration feature that allows javadoc to be
cross-linked. This may not work perfectly when linking to newly introduced
features across modules since I think the javadoc build consults the uploaded
documentation to determine the location to link to but for the most part it
will work and is the simplest and most reliable to configure.
I'll aim to get this done for 2.12.0 since I don't want to hold up cutting the
2.11.2 release
> javadoc link reference across modules don't work.
> -------------------------------------------------
>
> Key: JENA-683
> URL: https://issues.apache.org/jira/browse/JENA-683
> Project: Apache Jena
> Issue Type: Task
> Affects Versions: Jena 2.11.1
> Reporter: Andy Seaborne
> Assignee: Rob Vesse
> Fix For: Jena 2.12.0
>
>
> Reported in
> http://mail-archives.apache.org/mod_mbox/jena-users/201404.mbox/%3C20140418150631.A28042C1%40athena.apache.org%3E
> A link created is of the form:
> /module/apidocs/...class...
--
This message was sent by Atlassian JIRA
(v6.2#6252)
