[
https://issues.apache.org/jira/browse/SOLR-10361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432397#comment-17432397
]
Jan Høydahl commented on SOLR-10361:
------------------------------------
[~uschindler] seems like this has not been a real-life problem for a long time,
so let's close this JIRA?
We can make sure the smoketester actually build javadoc (I think it does), and
then print a comment at the end of the smoketester run, with the location of
the javadoc folder. Do you think it is a real issue that the Javadoc built on
the RMs machine will differ dramatically from the javadoc built on the
committer's machine?
> Add a solr-docs.tar.gz file
> ---------------------------
>
> Key: SOLR-10361
> URL: https://issues.apache.org/jira/browse/SOLR-10361
> Project: Solr
> Issue Type: Sub-task
> Components: documentation
> Reporter: Uwe Schindler
> Priority: Major
>
> On SOLR-9450 we decided to add a separate documentation package to the Solr
> downloads. I did something similar for forbiddenapis, too. This docs.tar.gz
> file should contain Lucene and Solr Javadocs.
> This would solve the following problems:
> - People can still download Javadocs, if they like to browse them offline,
> but it won't blow the release
> - The release manager has an easier job to push them to the website. The
> current process broke by SOLR-9450.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
