[
https://issues.apache.org/jira/browse/LUCENE-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303677#comment-17303677
]
Uwe Schindler commented on LUCENE-9849:
---------------------------------------
Solr's crossreferencing does not work at all at the moment. Because the links
are no longer local, the dependency walk to find the renderJavadocsPaths and
use their output does not work anymore. Solr is only referring to its own
modules automatically. For crosslinking to Lucene we would need a special case
(taking the lucene dependency coordinates and converting them to a link). But
that's another issue more belonging into Solr.
For Lucene, we have the logic already. If it is a release build, the absolute
https:// URL is used (see my above documentation.gradle snippet). We should
remove the links in the javadocs.jars, if we have no valid link. So in above
code, just set the solrJavadocsUrl to NULL and add some check in the parameter
builder (only add the inter-module link, if we have solrJavadocsUrl != null).
For the Maven Jenkins Build, I can add the system property pointing to the
javadocs in the artifact build. I am doing this now, then at least the
javadoc.jars are fine.
But indeed we should fix the above, so without some absolute HTTP we should not
add cross module links.
> Lucene snapshot javadocs are published with local URLs on jenkins
> -----------------------------------------------------------------
>
> Key: LUCENE-9849
> URL: https://issues.apache.org/jira/browse/LUCENE-9849
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Dawid Weiss
> Priority: Major
> Attachments: image-2021-03-17-08-55-19-726.png, screenshot-1.png
>
>
> !image-2021-03-17-08-55-19-726.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
