[
https://issues.apache.org/jira/browse/SOLR-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303959#comment-17303959
]
Dawid Weiss commented on SOLR-15265:
------------------------------------
Hi Chris. I added a PR showing how to fetch Lucene javadocs as maven artifacts
and unpack them locally. This should be enough to validate links, I think (but
I didn't take it any further).
bq. When you mention the cross-linking problem, are you concerned about the
more general link checking logic that the "documentation" task uses to make
sure we don't have broken links in the solr/lucene javadocs? ... I'm not really
familiar at all with how that works (is it recursive?)
I'm not really that familiar with it myself. What I meant by "cross-linking" is
that those Lucene javadocs we fetch from maven JARs will not be linked between
themselves. For non-snapshot releases they should be ok though as then javadocs
are rendered with links pointing to the final javadoc URL location.
> decide if/how to validate lucene javadoc links
> ----------------------------------------------
>
> Key: SOLR-15265
> URL: https://issues.apache.org/jira/browse/SOLR-15265
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Chris M. Hostetter
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> From parent issue...
> {quote}
> come up with a longer term plan for if/how we want to "validate" links to
> lucene javadocs
> * we currently don't do any validation of links to "remote" urls in the
> ref-guide content – regardless of wether they are hardcoded or version
> specific via ivy properties
> * we may want to revisit that now ... either in general, or via some lucene
> specific logic (possibly via fetching lucene src or javadoc jars) since we
> have so many links to lucene class javadocs
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
