[
https://issues.apache.org/jira/browse/SOLR-15262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301974#comment-17301974
]
Dawid Weiss commented on SOLR-15262:
------------------------------------
Hi Chris. Sorry I wasn't able to fix this myself - too little time. I knew
you're going to pick this up and felt guilty even back then...
Anyway:
* refactoring the URL prefix logic to pull the lucene version from ivy
properties (like we do for other 3rd party dependencies)
There is a comment in the build file that to some extent covers this - you can
get the exact Lucene version used at runtime (not at configuration time). So
you could construct those "remote" URLs with relative ease. The problem is that
Lucene doesn't publish snapshot javadocs anywhere so this doesn't really help
much.
I thought an alternative strategy could be to pull javadoc lucene artifacts
(jar files published by maven) and just unpack them locally to Solr
documentation... this would provide consistency and the ability to check
cross-links locally. And it's a relatively easy thing to do. If you need my
help there I can help out (a bit). Just confirm this is a direction you think
is worth exploring.
> deal with "local" ref-guide link checking after lucene/solr repo split
> ----------------------------------------------------------------------
>
> Key: SOLR-15262
> URL: https://issues.apache.org/jira/browse/SOLR-15262
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Chris M. Hostetter
> Assignee: Chris M. Hostetter
> Priority: Major
>
> The main goal of this issue (and some sub-tasks i expect to create) is to
> "fix" the way the ref-guide deals with links to lucene javadocs in the
> post-TLP split world where lucene src/javadoc links are not readily part of
> the solr repo
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
