[
https://issues.apache.org/jira/browse/SOLR-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973696#comment-13973696
]
Alexandre Rafalovitch commented on SOLR-5994:
---------------------------------------------
Javascript issues: I don't have specific reference, but it was something about
Javascript not loading properly when using local filesystem. May have been
fixed already. In any case, this is an enhancement, not bug fix, so a less
relevant part of conversation.
Admin link: Jetty will show the contexts when hitting root. So, that could be
minimal setup.
I agree on not expecting Javadoc in production. For example distribution, it
might be possible to use those admin-extra files to add the links for the
Javadoc (and online reference guide). Unless the various re-distributions keep
the example files but not Javadoc. But I don't know if those re-distributions
(e.g. Bitname) already break other expectations too.
If it were possible to integrate directly, a nice place to do the link to
Javadocs would be in something like an Analysis page and in Schema Browser.
Then, it becomes really important that the Javadoc is on the save server.
> Add Jetty configuration to serve JavaDocs
> ------------------------------------------
>
> Key: SOLR-5994
> URL: https://issues.apache.org/jira/browse/SOLR-5994
> Project: Solr
> Issue Type: Improvement
> Components: documentation, web gui
> Affects Versions: 4.7
> Reporter: Alexandre Rafalovitch
> Priority: Minor
> Labels: javadoc
> Fix For: 5.0
>
> Attachments: javadoc-jetty-context.xml
>
>
> It's possible to add another context file for Jetty that will serve Javadocs
> from the server.
> This avoids some Javascript issues, makes the documentation more visible, and
> opens the door for better integration in the future.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
