[
https://issues.apache.org/jira/browse/SOLR-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated SOLR-9450:
--------------------------------
Attachment: SOLR-9450.patch
Here is a more improved patch. As we changed the version properties in the
past, the way to detect an official "Solr" release is by comparing
{version.base} with {version} property. If they are identical, we have an
official release (that has doc on web page), otherwise it is some custom stuff
(e.g., snapshot or home-made builds like "6.5.0-ubuntu-pkg1").
Should I commit this or do you want to do this. I would reconfigure the Jenkins
Job building releases to pass its own JOB URL to the new property (next to
Lucene's Javadocs link).
> Link to online Javadocs instead of distributing with binary download
> --------------------------------------------------------------------
>
> Key: SOLR-9450
> URL: https://issues.apache.org/jira/browse/SOLR-9450
> Project: Solr
> Issue Type: Sub-task
> Components: Build
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Fix For: 6.5, master (7.0)
>
> Attachments: SOLR-9450.patch, SOLR-9450.patch, SOLR-9450.patch,
> SOLR-9450.patch, SOLR-9450.patch, SOLR-9450.patch
>
>
> Spinoff from SOLR-6806. This sub task will replace the contents of {{docs}}
> in the binary download with a link to the online JavaDocs. The build should
> make sure to generate a link to the correct version. I believe this is the
> correct tamplate: http://lucene.apache.org/solr/6_2_0/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
