[
https://issues.apache.org/jira/browse/SOLR-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris M. Hostetter updated SOLR-15265:
--------------------------------------
Description:
>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}
----
Resolution: Since lucene javadocs are readily available from maven, we just
unpack them and use them for local validation.
was:
>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}
> 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
> Assignee: Chris M. Hostetter
> Priority: Major
> Fix For: main (9.0)
>
> Attachments: SOLR-15265.patch
>
> Time Spent: 20m
> 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}
> ----
> Resolution: Since lucene javadocs are readily available from maven, we just
> unpack them and use them for local validation.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
